Bug 2529299 (CVE-2026-78254) - CVE-2026-78254 org.apache.ant/ant: Apache Ant: Arbitrary file write via path traversal in ftp and scp tasks
Summary: CVE-2026-78254 org.apache.ant/ant: Apache Ant: Arbitrary file write via path ...
Keywords:
Status: NEW
Alias: CVE-2026-78254
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2531705 2531706 2531709 2531710 2531711 2531712 2531713 2531714 2531715 2531716 2531707 2531708
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-07 07:51 UTC by OSIDB Bzimport
Modified: 2026-09-11 00:16 UTC (History)
31 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-07 07:51:25 UTC
The ftp and scp tasks of Apache Ant can download files from a remote server. A malicious server can provide relative paths that allow it to write outside of the dedicated target directory for the download, making it possible to overwrite files of the attacker's choice using the permissions of the user running Ant in versions prior to Ant 1.10.18. 




In order to exploit this vulnerability, the server would either have to be malicious or be subject to a machine-in-the-middle attack. Additionally in the case of scp or the ftp task using ftps the server must pass the server identity checks performed by the tasks.




For ftp tasks not using ftps a malicious server could act as a machine-in-the-middle to provide malicious files.




Starting with Ant 1.10.18 both tasks will prevent writing outside of the destination directory by default. An option is available to disable this behavior in the unlikely case that the  old behavior is required by existing build files.




Mitigations:




Users of scp and ftp (when using ftps) in any version of Ant should not bypass server identity checks. Users of ftp not using ftps should switch to ftps where possible.




All users are recommended to upgrade to Apache Ant 1.10.18, which fixes this issue.


Note You need to log in before you can comment on or make changes to this bug.