CVE-2026-95628: Path Traversal in Apache Camel

Path traversal in Apache Camel with public reproducer. Patches for supported versions. Admin action required.

CVE-2026-95628 is a path traversal vulnerability in the Camel Docling component of Apache Camel. The flaw affects how DoclingProducer handles the CamelDoclingCustomArguments header, containing custom arguments for the external docling tool. Incomplete validation (inherited from CVE-2026-40047) allows absolute paths to bypass checks, letting anyone controlling the header point the docling process to directories outside the working directory, if the Camel process has access.

CVSS is 5.4 (medium), but impact is concrete: admins exposing Camel routes to external input risk exploitation to access configurations, credentials, sensitive data outside the working directory. Public reproducer on GitHub (October 29, 2026) confirms reproducibility; no verified signals of active exploitation in the wild, but available code means immediate risk for deployments running Camel Docling.

Admins must verify their version: from 4.15.0 before 4.18.5 and from 4.19.0 before 4.22.2 are vulnerable. Upgrade to 4.23.0 (latest), 4.22.2 (4.22.x), or 4.18.5 (4.18.x). For those unable to upgrade immediately: do not build CamelDoclingCustomArguments from external input, configure JMS/Kafka consumers with default header filtering (they strip Camel.* headers), explicitly remove CamelDoclingCustomArguments from routes receiving messages from external systems to block the attack vector.

At a glance

What: Path traversal flaw in Apache Camel Docling component bypasses path validation; allows access to directories outside the working directory via custom arguments; affects CLI mode (default).
Severity: CVSS 5.4 (medium); requires ability to control the CamelDoclingCustomArguments header; real impact for admins exposing routes to external input.
Affected versions: Apache Camel from 4.15.0 before 4.18.5; from 4.19.0 before 4.22.2; release lines 4.15–4.17 and 4.19–4.21 reached end-of-life.
Fix: Update to 4.23.0 (latest), 4.22.2 (4.22.x), or 4.18.5 (4.18.x); 4.15–4.17 and 4.19–4.21 reached end-of-life.
Status: Public reproducer available on GitHub since October 29, 2026; not confirmed as actively exploited in the wild; patches available for all supported streams.
Action: Priority: verify Apache Camel usage; filter or remove CamelDoclingCustomArguments header from external messages; plan upgrade to supported version; configure consumers (JMS, Kafka) with default header filtering.

Sources: NVD, CVE-2026-95628

← All articles