CVE-2026-78254

7.4

Apache Software Foundation · Apache Ant

Apache Ant ftp and scp tasks are vulnerable to a path traversal flaw that allows a malicious server to overwrite arbitrary files outside the target directory using the permissions of the user.

Executive summary

A path traversal vulnerability in Apache Ant versions prior to 1.10.18 allows malicious servers to overwrite arbitrary files, posing a risk of unauthorized system modification.

Vulnerability

This is a relative path traversal vulnerability (CWE-23) occurring in the ftp and scp tasks. An attacker-controlled server can provide malicious paths during a download operation, allowing the software to write files outside the intended destination directory.

Business impact

By overwriting critical system files or application binaries, an attacker could potentially gain elevated privileges or impair service functionality. While the CVSS score of 7.4 indicates high severity, the requirement for a malicious or intercepted server connection moderates the immediate risk for well-secured environments.

Remediation

Immediate Action: Upgrade to Apache Ant version 1.10.18 or later, which includes new default protections against writing outside the destination directory.

Proactive Monitoring: Audit build configurations and ensure that server identity checks for scp and ftps tasks are enabled and strictly enforced.

Compensating Controls: Use secure transfer protocols like FTPS or SCP and ensure that all server identity verification settings are strictly configured to prevent man-in-the-middle attacks.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

All users of Apache Ant should update to version 1.10.18 immediately to benefit from the new security protections. Organizations should verify that their build pipelines are not bypassing server identity checks, as this is a critical defense against the conditions required to trigger this vulnerability.

More Apache Software Foundation CVEs

History

CVE Brief tracked this CVE 2 days before it had a CVSS score.

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. CVSS score assigned 7.4 (3.1)
  4. Analyst report written
  5. Analyst report updated
  6. Published in the daily brief high section, early-warning entry

Sources