cve.bz

CVE-2026-79985 apache software foundation apache camel: Path traversal

7.4 highEPSS 0.7%

High (7.4) in apache software foundation apache camel. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Camel SMB component. This issue affects Apache Camel: from 4.2.0 before 4.18.5, from 4.19.0 before 4.22.1. The Camel remote-file consumers poll a directory on a remote server and build the absolute remote path of each file by concatenating the configured directory with the file name reported in the server's directory listing. That concatenation (FtpUtils.absoluteFilePath and GenericFileConsumer) applied no lexical normalization and no check that the result stayed inside the directory being polled, and the resulting path became the operand for every subsequent remote operation on the file: retrieval (FtpOperations.retrieveFile / SftpOperations, reached from GenericFileConsumer where the retrieve name is taken verbatim from GenericFile.getAbsoluteFilePath), deletion when delete=true (GenericFileDeleteProcessStrategy), and renaming when move, preMove, moveFailed or readLock=rename is configured (GenericFileProcessStrategySupport and GenericFileRenameExclusiveReadLockStrategy). Neither isValidFile nor isMatched performed any containment check. A listing entry that is not a single path segment therefore resolved to a path outside the configured polling directory, causing Camel to read, delete or rename files outside it using the endpoint's own credentials. A listing name is not route-controlled data. It is supplied by the remote server, and the FTP control channel carries no integrity protection at all, so 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 such a name directly. Retrieval is reachable in a default consumer configuration, since the remote consumers download every listed file; deletion and renaming additionally require one of the disposition options above, all of which are common. Escape from the directory Camel was configured to poll is unconditional, while escape from the server's own account boundary additionally depends on whether that server confines the account. The jailStartingDirectory option, which is documented as restricting Camel to the starting directory and is enabled by default, governed producer writes and, since the localWorkDirectory containment work, consumer downloads to the local work directory - but it did not constrain this remote operand, so its name and description claimed a boundary that was not enforced here. The same entry point had already been recognised on the local side: the localWorkDirectory download path was constrained so that a remote file name containing parent-directory segments could not resolve outside the local work directory. The remote operand was the remaining half of that surface. This artifact provides the smb scheme. Its consumer walks the share listing on its own rather than through RemoteFileConsumer, skipping only the exact "." and ".." entries, so a name carrying traversal segments in any other form was concatenated unchecked. Reaching it requires a server that emits a listing name which is not a single path segment, which a conforming SMB2 implementation does not do; the exposure was corrected on the same basis as the other remote-file consumers rather than from a demonstrated proof of concept against this scheme. Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.22.x releases stream should upgrade to 4.22.1. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. The 4.14.x stream reached end of life and does not receive this fix; users on it should move to a supported releases stream.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.7% (unchanged from 0.7% a week ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-10-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-79985 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-79985?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-79985?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-79985 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • apache software foundation:apache camel

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.2.0 before 4.18.5
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.22.1

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated with an Important severity because untrusted directory data could allow an adversary controlling a remote file share to access, alter, or remove files outside the designated directory using the application's authenticated session. In Red Hat build of Apache Camel, exposure is confined to integration routes actively employing the optional camel-smb consumer to poll external shares. Under typical operational conditions, conforming SMB2 servers do not supply directory entries containing path traversal elements, meaning successful exploitation requires connecting to a compromised, rogue, or multi-tenant file server.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-10-20) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to enforce directory containment and boundary validation on remote directory listing paths within Camel remote-file consumers before invoking file retrieval or management operations: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Smb builds), which compact and verify that resolved remote paths remain within the starting directory, skipping non-conforming entries with a warning, closing all 3 injection vectors (crafted directory listing entries containing path traversal sequences, on-path modification of unencrypted directory listing responses, malicious or compromised remote file server responses). Until patched, this is a concern on Camel routes configured to poll remote files using remote-file consumer components, so restrict consumer connections to trusted remote servers, restrict file consumer include filters to single path segments, and disable destructive options such as delete or move on untrusted endpoints. As a compensating measure, canonicalize directory listing path segments before containment checks to eliminate unnormalized traversal tokens and deploy transport-layer encryption and integrity protection such as IPsec or WireGuard to prevent on-path tampering with directory listings. These controls limit blast radius and contain exploitation, but they do not fix the underlying path-traversal defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1301 Path Traversal Prevention (Canonicalization) (high)

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3camel-smbAffected
Red Hat build of Apache Camel for Spring Boot 4camel-smbAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-79985.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-79985 0 stars, Java, created
    Reproducer for CVE-2026-79985 (Apache Camel camel-smb): the SMB consumer builds the remote path from the share listing without containment …

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON