Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-79983 Overview
CVE-2026-79983 is a path traversal vulnerability [CWE-22] in the Apache Camel FTP component. The flaw affects the ftp, ftps, and sftp schemes used by Camel remote-file consumers. The consumers build absolute remote paths by concatenating the configured directory with file names reported in server directory listings, without lexical normalization or containment checks. A malicious listing entry can resolve to a path outside the configured polling directory, allowing attackers to read, delete, or rename files using the endpoint's credentials.
Critical Impact
An on-path attacker or malicious FTP server can manipulate LIST responses to force Apache Camel to retrieve, delete, or rename arbitrary files outside the intended polling directory.
Affected Products
- Apache Camel 4.0.0 through 4.18.4
- Apache Camel 4.19.0 through 4.22.0
- Apache Camel FTP, FTPS, and SFTP component schemes
Discovery Timeline
- 2026-10-19 - CVE-2026-79983 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-79983
Vulnerability Analysis
The vulnerability resides in how Apache Camel remote-file consumers construct absolute paths for files retrieved from FTP, FTPS, and SFTP servers. The FtpUtils.absoluteFilePath method and GenericFileConsumer concatenate the configured directory with the file name from the server's directory listing. Neither applies lexical normalization nor verifies that the resulting path remains within the polled directory.
The unvalidated path becomes the operand for every subsequent remote operation. This includes retrieval through FtpOperations.retrieveFile and SftpOperations, deletion when delete=true via GenericFileDeleteProcessStrategy, and renaming through GenericFileProcessStrategySupport when move, preMove, moveFailed, or readLock=rename is configured. The isValidFile and isMatched checks perform no containment validation.
Root Cause
The root cause is the absence of path containment enforcement on remote operands. The jailStartingDirectory option, enabled by default, documents a boundary that was not enforced for remote operations. It constrained producer writes and local work directory downloads, but not the remote operand on which Camel invokes retrieve, delete, and rename operations.
Attack Vector
Directory listing names are not route-controlled data. The FTP control channel provides no integrity protection, so an on-path attacker can rewrite a LIST response without credentials. A compromised, malicious, or multi-tenant FTP server can emit a crafted name directly. Retrieval is reachable in a default consumer configuration because remote consumers download every listed file. The reporter demonstrated end-to-end exploitation against an ftp endpoint using a malicious server whose LIST response named a file outside the polled directory. See the Apache Camel CVE-2026-79983 Advisory and the GitHub CVE-2026-79983 PoC for technical details.
Detection Methods for CVE-2026-79983
Indicators of Compromise
- FTP, FTPS, or SFTP server LIST responses containing file names with parent-directory segments such as ../ or absolute path prefixes.
- Unexpected file access, deletion, or rename operations on paths outside the configured Camel polling directory.
- Camel log entries referencing retrieved, deleted, or moved files whose resolved absolute paths escape the polled directory.
Detection Strategies
- Inspect Camel route logs for file names reported by remote consumers that contain path traversal sequences or non-segment path separators.
- Audit FTP, FTPS, and SFTP server logs for LIST responses issued toward Camel clients containing suspicious entries.
- Review file system access patterns on servers backing Camel endpoint accounts for operations touching paths outside expected working directories.
Monitoring Recommendations
- Monitor outbound FTP, FTPS, and SFTP sessions originating from systems running Apache Camel 4.0.0 through 4.22.0.
- Alert on Camel endpoint accounts performing retrieve, delete, or rename operations outside their intended directory scope.
- Capture directory listing payloads on untrusted FTP channels to identify tampered responses from on-path attackers.
How to Mitigate CVE-2026-79983
Immediate Actions Required
- Upgrade Apache Camel to version 4.23.0, 4.22.1, or 4.18.5 on all deployments using the FTP, FTPS, or SFTP components.
- Inventory all Camel routes using remote-file consumers to identify systems exposed through ftp, ftps, or sftp endpoints.
- Restrict Camel endpoint accounts on FTP servers to a confined chroot or jail where feasible, limiting the blast radius if traversal occurs.
Patch Information
Apache has released fixes in Camel 4.23.0, Camel 4.22.1 for the 4.22.x stream, and Camel 4.18.5 for the 4.18.x LTS stream. The 4.14.x stream reached end of life and does not receive this fix; users should migrate to a supported release stream. See the fix commits in GitHub Pull Request #25730, GitHub Pull Request #25745, GitHub Pull Request #25746, and GitHub Pull Request #25747. Reference the Apache JIRA Issue CAMEL-24487 for issue tracking.
Workarounds
- Use SFTP over SSH with verified host keys instead of plaintext FTP to defeat on-path LIST tampering, while recognizing this does not mitigate malicious or compromised servers.
- Confine Camel endpoint accounts at the FTP server to a chroot that prevents escape from the server-side account boundary.
- Avoid using Camel remote-file consumers against untrusted or multi-tenant FTP servers until upgrading to a fixed release.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

