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-79986 Overview
CVE-2026-79986 is a path traversal vulnerability [CWE-22] in the Apache Camel Azure Files component. The flaw resides in the remote-file consumer logic shared across Camel's remote-file endpoints. Camel builds the absolute remote path of each file by concatenating the configured polling directory with the file name from the server's directory listing. The concatenation helpers FtpUtils.absoluteFilePath and GenericFileConsumer apply no lexical normalization and no containment check. A malicious listing entry resolves to a path outside the configured polling directory. The resulting operand drives retrieval, deletion, and rename operations under the endpoint's credentials.
Critical Impact
An on-path attacker or malicious remote server can supply crafted directory listing entries that cause Camel to read, delete, or rename files outside the configured polling directory using the endpoint's own credentials.
Affected Products
- Apache Camel 4.0.0 before 4.18.5
- Apache Camel 4.19.0 before 4.22.1
- Apache Camel camel-azure-files component
Discovery Timeline
- 2026-10-19 - CVE-2026-79986 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-79986
Vulnerability Analysis
The vulnerability lives in Camel's remote-file consumer base class, which the camel-azure-files component inherits. When the consumer polls a remote directory, it reads each entry returned by the server and constructs the operand path through plain string concatenation. Neither isValidFile nor isMatched validates that the resulting path stays within the configured directory.
The unsafe operand then flows into FtpOperations.retrieveFile, SftpOperations, GenericFileDeleteProcessStrategy, GenericFileProcessStrategySupport, and GenericFileRenameExclusiveReadLockStrategy. Retrieval is reachable with a default consumer configuration because remote consumers download every listed file. Deletion and renaming become reachable when delete=true, move, preMove, moveFailed, or readLock=rename is configured.
The jailStartingDirectory option, enabled by default and documented as restricting Camel to the starting directory, did not constrain the remote operand. Its name and description claimed a boundary that was not enforced on remote operations.
Root Cause
The root cause is missing lexical normalization and missing containment checks on remote path construction. A listing name is not route-controlled data. It is supplied by the remote server. Camel treated server-supplied names as trusted single-segment file names without verifying this property.
Attack Vector
The FTP control channel carries no integrity protection. An on-path attacker can rewrite a LIST response without holding any credentials. A compromised, malicious, or multi-tenant server, or a server backed by a virtual filesystem, can emit a crafted listing name directly. For the camel-azure-files component, reaching the flaw requires a listing name that is not a single path segment. The Azure Files REST service does not normally return such names, so the fix was applied for parity with the other remote-file consumers rather than from a demonstrated proof of concept. See the Apache Camel CVE-2026-79986 Advisory for additional detail.
Detection Methods for CVE-2026-79986
Indicators of Compromise
- Remote file consumer logs showing retrieved, deleted, or renamed file names containing ../ or absolute path prefixes.
- Camel endpoint credentials accessing files outside the configured polling directory on the remote server.
- Unexpected RETR, DELE, or RNFR/RNTO operations in FTP server logs targeting paths above the account's working directory.
Detection Strategies
- Enable verbose logging on Camel remote-file consumers and alert on file names resolved outside the configured directoryName.
- Inspect FTP, SFTP, and Azure Files access logs for listing responses containing multi-segment names or parent-directory references.
- Audit Camel route definitions for use of move, preMove, moveFailed, delete=true, or readLock=rename dispositions on remote-file endpoints.
Monitoring Recommendations
- Correlate Camel application logs with remote server access logs to identify operations on paths outside expected directories.
- Monitor for anomalous file deletion or rename volume on remote servers accessed by Camel integration accounts.
- Track Camel version inventory across deployments and flag instances running affected 4.x releases.
How to Mitigate CVE-2026-79986
Immediate Actions Required
- Upgrade Apache Camel to version 4.23.0, 4.22.1, or 4.18.5 depending on the release stream in use.
- Migrate from the end-of-life 4.14.x stream to a supported release that receives this fix.
- Review all Camel routes that consume from FTP, SFTP, or Azure Files endpoints and audit disposition options.
Patch Information
The fix is delivered in Apache Camel 4.23.0, 4.22.1, and 4.18.5. Patch details are published in GitHub Pull Request #25730, #25745, #25746, and #25747. Tracking is maintained in Apache Camel JIRA Issue CAMEL-24487.
Workarounds
- Restrict the server-side account used by Camel so that even successful escape from the polling directory cannot leave the account's confinement.
- Use SFTP with host key verification instead of plain FTP to prevent on-path tampering of listing responses.
- Avoid pointing Camel consumers at multi-tenant or untrusted remote servers until upgrades are deployed.
# Upgrade example for Maven-based Camel projects
mvn versions:set-property -Dproperty=camel.version -DnewVersion=4.23.0
mvn clean install
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

