CVE-2026-95628: Apache Camel Docling component path traversal

CVE-2026-95628 · Severity: medium · CVSS 5.4 · Published 2026-10-26

Apache Camel's Docling component, used to convert documents to various formats, contains a path traversal vulnerability in how it processes custom command-line arguments. An attacker who can influence the CamelDoclingCustomArguments header could direct the docling process to access files or directories outside the intended working directory, potentially exposing sensitive data or enabling further compromise.

Technologies: Apache Camel. Vendors: Apache.

Quick answers

Is CVE-2026-95628 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-95628 being exploited in the wild.
How severe is CVE-2026-95628?
Medium severity, with a CVSS score of 5.4, published 26 October 2026.
Which products and versions are affected?
Apache Camel 4.15.0 to 4.18.4, 4.19.0 to 4.22.1.
Is there a fix for CVE-2026-95628?
Yes: fixed in 4.23.0, 4.22.2, 4.18.5. Until then: Do not construct the CamelDoclingCustomArguments header from untrusted external input; remove that header from incoming messages before they reach a docling endpoint; ensure message consumers apply Camel's default header filtering so that only routes themselves control custom arguments. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-95628 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-95628?
Check whether you run Apache Camel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 4.23.0, 4.22.2, 4.18.5

Do not construct the CamelDoclingCustomArguments header from untrusted external input; remove that header from incoming messages before they reach a docling endpoint; ensure message consumers apply Camel's default header filtering so that only routes themselves control custom arguments.

Technical details

The vulnerability stems from incomplete path validation in DoclingProducer's validatePathSafety method, which rejects relative traversal sequences like ../ but fails to block absolute paths. An attacker supplying an absolute path in the CamelDoclingCustomArguments header (such as via the --artifacts-path flag) can bypass the restriction intended by a prior CVE-2026-40047 fix and access any directory readable by the Camel process. This requires the attacker to influence the header value through route configuration or incoming message headers without Camel's default filtering.

Affected products

  • Apache Camel 4.15.0 to 4.18.4, 4.19.0 to 4.22.1

Timeline

  • 2026-10-26: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.