Technical impact
The CamelDoclingOutputFilePath header is passed verbatim to the external docling CLI tool’s --output flag without normalization or restriction. An attacker able to influence this header can cause docling to write the converted document to any directory the Camel process can write to. This leads to arbitrary file creation with content derived from an externally supplied document, potentially enabling sensitive data exfiltration or placement of malicious artifacts. The flaw is a classic Path Traversal issue classified as CWE‑22 and gives the attacker write access to system files rather than execution rights.
Affected Systems
The vulnerability affects Apache Camel from version 4.15.0 up to but not including 4.18.5, and from 4.19.0 up to but not including 4.22.2. Supported releases that contain the fix are 4.18.5, 4.22.2, and any version from the 4.23.0 line onward. Older release lines such as 4.15.x‑4.17.x and 4.19.x‑4.21.x have reached end of life and will not receive a patch, so they require an upgrade to a supported release.
Risk and Exploitability
With a CVSS score of 5.4 the vulnerability is considered medium severity. There is no EPSS score available, and the issue is not listed in the CISA KEV catalog, suggesting a lower likelihood of widespread, automated exploitation. Nonetheless, the flaw can be exploited in any scenario where inbound message headers are accepted without sanitization, and an attacker who can inject the CamelDoclingOutputFilePath header can redirect output to arbitrary directories, potentially creating or overwriting critical files.