CVE-2026-40047
Last modified
CVE-2026-40047 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. 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. EPSS estimates a 1.26% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Camel | >= 4.15.0, < 4.18.3 |
References
- https://camel.apache.org/security/CVE-2026-40047.htmlVendor Advisory
- http://www.openwall.com/lists/oss-security/2026/07/05/2Mailing List, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-40047?
How severe is CVE-2026-40047?
How do I fix CVE-2026-40047?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-40041Pachno 1.0.6 contains a cross-site request forgery vulnerabi…5.3
- CVE-2026-40042Pachno 1.0.6 contains an XML external entity injection vulne…9.8
- CVE-2026-40043Pachno 1.0.6 contains an authentication bypass vulnerability…7.1
- CVE-2026-40044Pachno 1.0.6 contains a deserialization vulnerability that a…9.8
- CVE-2026-40045OpenClaw before 2026.4.2 accepts non-loopback cleartext ws:/…5.9
- CVE-2026-40046Integer Overflow or Wraparound vulnerability in Apache Activ…7.5
- CVE-2026-40048The Camel-PQC FileBasedKeyLifecycleManager class deserialize…7.8
- CVE-2026-4005The Coachific Shortcode plugin for WordPress is vulnerable t…6.4
- CVE-2026-40050CrowdStrike has released security updates to address a criti…9.8
- CVE-2026-4006The Simple Draft List plugin for WordPress is vulnerable to …6.4
- CVE-2026-40060When a BIG-IP Advanced WAF or ASM security policy is configu…8.7
- CVE-2026-40061When BIG-IP DNS is provisioned, a vulnerability exists in an…8.7
Are you affected by CVE-2026-40047?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
