On this page
CVE Details
- Protection status: Protected by Atomicorp rules · About protection statuses
- CVE: CVE-2026-95628
- Name: Apache Camel: Camel-Docling Custom CLI Argument Path Validation Does Not Reject Absolute Paths (Incomplete Fix of CVE-20
- Severity: Medium
- CVSS: 5.4 (v3.1) (Medium)
- CVSS version: 3.1
- CVSS source: apache CNA
- CVSS vector:
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 impact: None
- Integrity impact: Low
- Availability impact: Low
- CWE: CWE-22 — Improper Limitation of a Pathname to a Restricted Directory
- Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-126 (opens in a new tab) , CAPEC-64 (opens in a new tab) , CAPEC-76 (opens in a new tab) , CAPEC-78 (opens in a new tab) , CAPEC-79 (opens in a new tab)
- Vendor: apache
- Vulnerable product: camel
- CVE published: 2026-10-26
- CVE last modified: 2026-11-06
- Affected versions (NVD configurations):
- camel: >= 4.15.0, < 4.18.5
- camel: >= 4.19.0, < 4.22.2
- EPSS: 0.0100; 63.6th percentile as of 2026-11-20 (FIRST (opens in a new tab) )
- Latest Update: 2026-11-10
- Selected Rule IDs observed: 340006 , 390719
- Matching rules: 2; rules with blocking actions: 2
- Would-block Rule IDs: 340006 , 390719
- Request surfaces inspected: Request filename, Request headers
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data
CVSS assessments
CVSS v3.1 · security@apache.org
- Base score: 5.4
- Base severity: MEDIUM
- Exploitability subscore: 2.8
- Impact subscore: 2.5
- Assessment type: Secondary
- Source identifier: security@apache.org
- Full vector:
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 impact: None
- Integrity impact: Low
- Availability impact: Low
- Exploit maturity: Not scored
Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.
Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)
CISA SSVC assessments
These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.
- Provider: CISA ADP
- Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
- SSVC version: 2.0.3
- Role: CISA Coordinator
- Assessment timestamp: 2026-10-26T14:12:52.898968Z
- Exploitation: none
- Automatable: no
- Technical Impact: partial
- Source: CISA ADP in the CVE record (opens in a new tab)
Vulnerable CPE configurations
cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*- Version start (inclusive):
4.15.0 - Version end (exclusive):
4.18.5 - NVD match criteria ID:
DFCBEBCC-485B-4426-AF9B-6494D5248B3B
- Version start (inclusive):
cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*- Version start (inclusive):
4.19.0 - Version end (exclusive):
4.22.2 - NVD match criteria ID:
98F17F8D-EF4C-4F95-8EF6-206920C39E30
- Version start (inclusive):
Vulnerability Description
Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’) vulnerability in Apache Camel Docling component.
This issue affects Apache Camel: from 4.15.0 before 4.18.5, from 4.19.0 before 4.22.2.
DoclingProducer builds the command line of the external docling tool and appends to it the custom arguments supplied in the CamelDoclingCustomArguments header, a list of strings whose flags the fix for CVE-2026-40047 restricted to an allowlist. That fix also introduced validatePathSafety to keep path-like argument values inside the intended directory, but the method only looked for relative traversal: it rejected a value containing a traversal sequence such as ../ and a value whose normalized form still held a .. element. It never checked whether a value was an absolute path, and an absolute path without traversal segments contains neither, so it passed unchanged. Every path-like value went through this check, whether it was a separate list element following its flag or was attached to the flag after an equals sign, so an absolute path was accepted in either form, for example as the directory given to the allowlisted –artifacts-path flag, which tells docling where to find its model artifacts. Such a value reached the docling command line as given, so a party able to choose the custom arguments could point the docling process at any directory the Camel process can access, outside the working directory that the check was meant to keep path values in, which is the outcome the CVE-2026-40047 fix set out to prevent. Only the CLI mode, which is the default, passes custom arguments to docling. The header belongs to the Camel header namespace, which consumers applying Camel’s default header filtering, such as the JMS and Kafka consumers, remove from incoming messages, so the issue is reached where a route forwards externally influenced values into the header or where a consumer maps incoming headers without that filtering.
Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.2. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The 4.15.x to 4.17.x and 4.19.x to 4.21.x release lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release. For deployments that cannot upgrade immediately, do not build the CamelDoclingCustomArguments header from values that originate outside the deployment, remove that header from messages that arrive from outside before they reach a docling endpoint, and make sure that consumers which map incoming message headers drop the Camel header namespace, so that only the route itself chooses the custom arguments.
Recommended Actions
Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340006 , 390719 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.
Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.
- Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.18.5.
- Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.22.2.
- Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.18.5 or later.
- Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.22.2 or later.
- CNA guidance source: apache (opens in a new tab)
- Vendor recommendation: Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.22.x stream should upgrade to 4.22.2 and users on the 4.18.x stream should upgrade to 4.18.5. The validatePathSafety helper now also rejects a path-like custom-argument value that is an absolute path, whether it is given as a separate list element or attached to its flag, so every path-valued flag on the allowlist is covered; a relative value without traversal segments is still accepted. The 4.15.x to 4.17.x and 4.19.x to 4.21.x release lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release.
- Vendor workaround: Do not build the CamelDoclingCustomArguments header from values that originate outside the deployment, remove that header from messages that arrive from outside before they reach a docling endpoint, and make sure that consumers which map incoming message headers drop the Camel header namespace, so that only the route itself chooses the custom arguments.
Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.
Research Notes
Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.
Public Vulnerability References
- NVD (opens in a new tab)
- CVE Record (opens in a new tab)
- CVE authority reference: https://camel.apache.org/security/CVE-2026-40047.html (opens in a new tab)
- CVE authority reference: https://camel.apache.org/security/CVE-2026-78163.html (opens in a new tab)
- Vendor advisory: https://camel.apache.org/security/CVE-2026-95628.html (opens in a new tab)
- Patch or mitigation: https://github.com/apache/camel/pull/26738 (opens in a new tab)
- Patch or mitigation: https://github.com/apache/camel/pull/26743 (opens in a new tab)
- Patch or mitigation: https://github.com/apache/camel/pull/26744 (opens in a new tab)
- Vendor advisory: https://issues.apache.org/jira/browse/CAMEL-24893 (opens in a new tab)
Test or Research Source
- Source: Atomicorp AI Research Framework
- Tags: cve, derived, traversal, waf-probe
Research Note Context
This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.
Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.
Learn More
Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.
Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:
- Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
- Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
- Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
- Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
- Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.
For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .