---
title: "CVE-2026-40047: Apache Camel-Docling: Insufficient validation of custom CLI arguments enables argument injection and path traversal in DoclingProducer"
url: https://erroneo.us/security/cve/CVE-2026-40047/
description: "CVE-2026-40047 (org.apache.camel:camel-docling (Maven)): Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') vulnerability in…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-07-06
date_modified: 2026-08-26
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-40047"
kev: false
cvss: 9.1
epss: 0.02429
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-40047: Apache Camel-Docling: Insufficient validation of custom CLI arguments enables argument injection and path traversal in DoclingProducer

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 2.4% , percentile 84: FIRST’s model estimates a 2.4% chance of exploitation activity in the next 30 days, higher than 84% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes org.apache.camel:camel-docling (Maven) >= 4.15.0, < 4.18.3, fixed in 4.18.3 . Check your lockfile, including transitive dependencies.

## What it is

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 ) 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…

## Affected packages

- Maven `org.apache.camel:camel-docling` >= 4.15.0, < 4.18.3 → fixed: 4.18.3

## Affected products (CVE record)

- Apache Software Foundation Apache Camel: 4.15.0 < 4.18.3

## Severity

- CISA-ADP CVSS 3.1: 9.1 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`
- GitHub CVSS 3.1: 9.1 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none , automatable no , technical impact total .
- FIRST EPSS (model of 2026-10-21): 2.43% probability of exploitation activity in the next 30 days; percentile 84.

## Sources

- [camel.apache.org](https://camel.apache.org/security/CVE-2026-40047.html)
- [GitHub Advisory GHSA-rpv3-6645-2vqc](https://github.com/advisories/GHSA-rpv3-6645-2vqc)
- [CVE.org record CVE-2026-40047](https://www.cve.org/CVERecord?id=CVE-2026-40047)
- [NVD entry CVE-2026-40047](https://nvd.nist.gov/vuln/detail/CVE-2026-40047)
- [openwall.com](http://www.openwall.com/lists/oss-security/2026/07/05/2)
- [github.com](https://github.com/apache/camel/pull/22082)
- [github.com](https://github.com/apache/camel/pull/22767)
- [github.com](https://github.com/apache/camel/commit/1fa56f45901f50aa79849ff2d2ca83dd57f6991c)
- [github.com](https://github.com/apache/camel/commit/f86fda0442c65b9d13ce3aa8ac676233b64e3351)
- [github.com](https://github.com/apache/camel/releases/tag/camel-4.18.3)
- [github.com](https://github.com/apache/camel/releases/tag/camel-4.19.0)
- [issues.apache.org](https://issues.apache.org/jira/browse/CAMEL-23212)

---
Source page: https://erroneo.us/security/cve/CVE-2026-40047/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt