VulnerabilityPublished 26 Oct 2026

CVE-2026-95629: Apache Camel · Path Traversal

Affects Apache CamelSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 4.22.2 or 4.18.5 when convenient.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.22.2, 4.18.5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache to 4.22.2 or 4.18.5.

Affected software

Product	Affected	Fixed in
Apache Camelorg.apache.camel:camel-docling	Affected >=4.19.0 <4.22.2	Fixed in 4.22.2
Apache Camelorg.apache.camel:camel-docling	Affected >=4.15.0 <4.18.5	Fixed in 4.18.5
MavenApache Software Foundation/org.apache.camel:camel-docling`pkg:maven/Apache Software Foundation/org.apache.camel:camel-docling`Other threats	Affected >=4.15.0 <4.18.5 >=4.19.0 <4.22.2	Fixed in 4.18.5 4.22.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Apache Camel versions 4.18.5 and 4.22.2. Users should upgrade to these versions or later (such as 4.23.0). After upgrading, set the outputBaseDirectory endpoint option on all docling endpoints where the CamelDoclingOutputFilePath header can be influenced externally to restrict output paths. For deployments that cannot upgrade immediately, do not allow external input to build the CamelDoclingOutputFilePath header, remove this header from incoming messages from outside the deployment before they reach a docling endpoint, and ensure consumers that map incoming headers drop the Camel header namespace to prevent unfiltered header forwarding.

Description

CVE-2026-95629 is a path traversal vulnerability in the Apache Camel Docling component affecting versions from 4.15.0 before 4.18.5 and from 4.19.0 before 4.22.2. The issue arises because the CamelDoclingOutputFilePath header value is passed verbatim to the external docling tool's --output flag without proper normalization or directory confinement, allowing an attacker able to set this header to write conversion output files to arbitrary writable directories. The vulnerability is fixed in Apache Camel versions 4.18.5 and 4.22.2 with the introduction of an outputBaseDirectory option to restrict output paths. Users are advised to upgrade to these fixed versions and configure the new option if the header can be influenced externally. For those unable to upgrade immediately, mitigating controls include sanitizing or removing the header from external inputs and ensuring header filtering is applied.

Impact

An attacker able to set the CamelDoclingOutputFilePath header can cause the DoclingProducer to write converted document output files to arbitrary directories writable by the Camel process. This could lead to unauthorized file creation or modification, potentially impacting integrity and availability. The vulnerability does not disclose data directly but allows placing crafted files on the system. The CVSS 3.1 score is 5.4 (medium), reflecting network attack vector, low complexity, low privileges required, no user interaction, unchanged scope, no confidentiality impact, low integrity impact, and low availability impact.

Summary

This vulnerability in Apache Camel's DoclingProducer component allows path traversal via the CamelDoclingOutputFilePath header, which is passed directly to the docling tool's --output flag without normalization or confinement. This enables writing conversion output files to arbitrary directories writable by the Camel process. The issue affects Apache Camel versions >=4.15.0 <4.18.5 and >=4.19.0 <4.22.2. The fix, available in versions 4.18.5 and 4.22.2, adds an outputBaseDirectory endpoint option to restrict output locations. The vulnerability can be exploited if an attacker can set the vulnerable header, which is normally filtered by default consumers but may be forwarded by routes or consumers without filtering. The docling-serve mode is not affected. Users should upgrade and configure the new option or apply header filtering and sanitization as interim mitigations.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 09:01 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats