# CVE-2026-95629: Apache Camel Docling path traversal in output directory

Source: https://junglewise.ai/threats/cve-2026-95629-improper-limitation-of-a-pathname-to-a-restricted-directory-path  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-26. Updated: 2026-10-26  
License: CC BY 4.0 with a link back

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

Apache Camel's Docling component converts documents to various formats. An attacker who can influence the CamelDoclingOutputFilePath header can write the converted document to any directory the Camel process has write access to, potentially exposing sensitive data or disrupting operations by placing files in unexpected locations.

Technologies: [Apache Camel](https://junglewise.ai/threats/technologies/camel). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-95629 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-95629 being exploited in the wild.

**How severe is CVE-2026-95629?** Medium severity, with a CVSS score of 5.4, published 26 October 2026.

**Which products and versions are affected?** Apache Camel 4.15.0 before 4.18.5, 4.19.0 before 4.22.2.

**Is there a fix for CVE-2026-95629?** Yes: fixed in Apache Camel 4.23.0, 4.22.2, 4.18.5. Until then: Set the outputBaseDirectory endpoint option on every docling endpoint after upgrading to confine output to a specific directory. Do not construct the CamelDoclingOutputFilePath header from external values; remove this header from externally-sourced messages before they reach a docling endpoint; and ensure message consumers drop the Camel header namespace so only the route itself controls the output directory. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-95629 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-95629?** 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 Apache Camel 4.23.0, 4.22.2, 4.18.5

Set the outputBaseDirectory endpoint option on every docling endpoint after upgrading to confine output to a specific directory. Do not construct the CamelDoclingOutputFilePath header from external values; remove this header from externally-sourced messages before they reach a docling endpoint; and ensure message consumers drop the Camel header namespace so only the route itself controls the output directory.

## Technical details

The DoclingProducer component fails to normalize or validate the CamelDoclingOutputFilePath header before passing it to the external docling tool's --output flag, allowing absolute paths and directory traversal sequences (..) to bypass intended directory confinement. The vulnerability is exploitable where routes forward externally-influenced header values or where consumers map incoming headers without Camel's default filtering that would normally strip the Camel header namespace. JMS and Kafka consumers remove Camel headers by default, limiting exposure in those cases.

## Affected products

- Apache Camel 4.15.0 before 4.18.5, 4.19.0 before 4.22.2

## Timeline

- 2026-10-26: disclosed

## Related threats

- [Apache Camel SSRF in A2A webhook validator](https://junglewise.ai/threats/cve-2026-71569-server-side-request-forgery-ssrf-vulnerability-in-apache-camel)
- [Apache Camel OAuth component cache containing sensitive information](https://junglewise.ai/threats/cve-2026-94386-use-of-cache-containing-sensitive-information-vulnerability-in)
- [Apache Camel Saxon component XXE in XQuery evaluation](https://junglewise.ai/threats/cve-2026-90885-improper-restriction-of-xml-external-entity-reference)
- [Apache Camel AWS2-S3 expression language injection in key handling](https://junglewise.ai/threats/cve-2026-95664-improper-neutralization-of-special-elements-used-in-an-expression)
- [Apache Camel Keycloak security policy token expiration bypass](https://junglewise.ai/threats/cve-2026-95663-insufficient-session-expiration-vulnerability-in-apache-camel)