Apache Software Foundation Apache Camel: command injection

Apache Software Foundation Apache Camel

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.

Fix it

Apache Camel

Upgrade to Apache Camel 4.18.3

org.apache.camel:camel-docling maven

mvn versions:use-dep-version -Dincludes=org.apache.camel:camel-docling -DdepVersion=4.18.3 -DforceVersion=true

First seen: 29 Oct 2026
Last update: 29 Oct 2026, 10:18 UTC
Fixed in: org.apache.camel:camel-docling 4.18.3
Apache Camel 4.18.3
Identifiers: CVE-2026-40047
CVSS: 9.1
Source: news
On the menu as: Java

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Apache Software Foundation Apache Camel: command injection
Severity: critical. Patch status: patched.
Affected: Apache Software Foundation Apache Camel
Fixed in: org.apache.camel:camel-docling 4.18.3, Apache Camel 4.18.3
Ids: CVE-2026-40047

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.

## Steps
1. Search every lockfile and manifest (package-lock.json, yarn.lock, pnpm-lock.yaml, requirements*.txt, poetry.lock, uv.lock, composer.lock, go.sum, Cargo.lock, Gemfile.lock) for `org.apache.camel:camel-docling`. For each hit, compare the installed version with the fix on the same major line: org.apache.camel:camel-docling 4.18.3, Apache Camel 4.18.3. If it's lower, give the exact upgrade command for the package manager this repo uses.
2. Fix by release line: org.apache.camel:camel-docling: >= 4.15.0 < 4.18.3 → 4.18.3. Apache Camel: 4.18.3.

## Fix by release line
| Line | State | Fix | Until then |
|---|---|---|---|
| org.apache.camel:camel-docling >= 4.15.0 < 4.18.3 | fixed | 4.18.3 | — |
| Apache Camel | fixed | 4.18.3 | — |

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve("CVE-2026-40047") for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://camel.apache.org/security/CVE-2026-40047.html https://nvd.nist.gov/vuln/detail/CVE-2026-40047
https://pwned.coffee/i/apache-camel-docling-critical-vulnerability-cve-2026-40047

Timeline

29 Oct 2026, 10:18 UTC
Fix status: unknown → patched.
29 Oct 2026
First reported.

Receipt

Exploitation: No known exploitation
Fix by release line: Product Affected Fixed in Source
org.apache.camel:camel-docling (maven) >= 4.15.0, < 4.18.3 4.18.3 GitHub advisory checked 29 Oct
Apache Camel before 4.18.3 4.18.3 CVE record (CNA) checked 29 Oct
Score: CVSS 9.1 (critical). CVSS 3.1 9.1 (CISA ADP) for CVE-2026-40047
Last checked: 29 Oct 2026, 10:18 UTC

Product	Affected	Fixed in	Source
org.apache.camel:camel-docling (maven)	>= 4.15.0, < 4.18.3	4.18.3	GitHub advisory checked 29 Oct
Apache Camel	before 4.18.3	4.18.3	CVE record (CNA) checked 29 Oct

Sources: KEV – CVE record ✓ Vendor ✓

Sources

Wrong fix version, or a source we missed? Send it back to chef@pwned.coffee with the source, and we'll correct it here.

Totalone very hot coffee