On this page
CVE Details
- Protection status: Protected by Atomicorp rules · About protection statuses
- CVE: CVE-2026-40047
- Name: Apache Camel: Camel-Docling: Insufficient validation of custom CLI arguments enables argument injection and path travers
- Severity: Critical
- CVSS: 9.1 (v3.1) (Critical)
- CVSS version: 3.1
- CVSS source: CISA ADP
- CVSS vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N- Attack vector: Network
- Attack complexity: Low
- Privileges required: None
- User interaction: None
- Scope: Unchanged
- Confidentiality impact: High
- Integrity impact: High
- Availability impact: None
- CWE: CWE-88 — Improper Neutralization of Argument Delimiters in a Command
- Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-137 (opens in a new tab) , CAPEC-174 (opens in a new tab) , CAPEC-41 (opens in a new tab) , CAPEC-460 (opens in a new tab) , CAPEC-88 (opens in a new tab)
- Vendor: apache
- Vulnerable product: camel
- CVE published: 2026-07-06
- CVE last modified: 2026-10-25
- Affected versions (NVD configurations):
- camel: >= 4.15.0, < 4.18.3
- EPSS: 0.0243; 84.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 · CISA ADP
- Base score: 9.1
- Base severity: CRITICAL
- Exploitability subscore: 3.9
- Impact subscore: 5.2
- Assessment type: Secondary
- Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
- Full vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N- Attack vector: Network
- Attack complexity: Low
- Privileges required: None
- User interaction: None
- Scope: Unchanged
- Confidentiality impact: High
- Integrity impact: High
- Availability impact: None
- 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-07-06T18:48:56.576065Z
- Exploitation: none
- Automatable: no
- Technical Impact: total
- 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.3 - NVD match criteria ID:
0AEE4159-4465-4ACD-B94A-1E4682C85270
- Version start (inclusive):
Vulnerability Description
Improper Neutralization of Argument Delimiters in a Command (‘Argument Injection’) vulnerability in Apache Camel Docling component.
The camel-docling component invokes the external docling command-line tool by assembling an argument list in DoclingProducer and executing it through java.lang.ProcessBuilder. Custom CLI arguments supplied through the CamelDoclingCustomArguments exchange header (a List<String>) were appended to that argument list with insufficient validation: the original implementation relied on a denylist of disallowed flags and only rejected path values that contained a literal ../ sequence. As a result, a Camel route that forwards externally-influenced data into the CamelDoclingCustomArguments header (or into the path-bearing headers used to build the invocation) could cause the producer to pass unrecognized or unintended docling CLI flags to the subprocess, and could supply path-like argument values that resolved outside the intended directory through traversal sequences not caught by the literal ../ check. Because Camel itself builds the docling invocation from these values, the component is responsible for constraining them, and the weak validation allowed CLI-argument injection and directory traversal in the arguments passed to the external tool. The invocation uses the list-based form of ProcessBuilder, so a shell does not interpret the argument values; OS command injection through shell metacharacters was not possible, and the metacharacter rejection added by the fix is defense-in-depth.
This issue affects Apache Camel: from 4.15.0 before 4.18.3.
Users are recommended to upgrade to a release that contains the CAMEL-23212 fix. On the mainline the fix is included from Apache Camel 4.19.0 (and later releases such as 4.20.0). For users on the 4.18.x LTS releases stream, upgrade to 4.18.3. The fix replaces the denylist with a strict allowlist of recognized docling CLI flags (rejecting any unrecognized flag, and rejecting producer-managed flags such as the output-directory flags), defensively rejects shell metacharacters in argument values, and normalizes path-like values with Path.normalize() before validating them so that traversal sequences which bypass a literal ../ check are detected. As defence in depth, route authors should avoid mapping untrusted message content into the CamelDoclingCustomArguments header and the path-bearing headers, and should strip Camel-internal headers from messages that arrive from untrusted producers.
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.3.
- Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.18.3 or later.
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)
- Vendor advisory: https://camel.apache.org/security/CVE-2026-40047.html (opens in a new tab)
- Exploit or technical research: http://www.openwall.com/lists/oss-security/2026/07/05/2 (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) .