CVE-2026-95629
Description
A flaw was found in the camel-docling component of Apache Camel. The component fails to validate or sanitize directory paths specified in message headers before passing them to the underlying document conversion tool. An attacker able to influence message headers can exploit this path traversal issue to write conversion output files to arbitrary directories accessible to the application process, potentially leading to unauthorized file creation and compromising system integrity.
Statement
This vulnerability is rated as Moderate impact because successful exploitation requires non-default integration routes that forward untrusted input into internal Camel message headers, which standard consumers strip automatically. Furthermore, the arbitrary file creation cannot be leveraged to write raw payloads, as the generated output is restricted to converted document markup and text formatted under generated file names. Deployments using docling-serve mode or standard header filtering mechanisms remain unaffected.
Mitigation
Do not build the CamelDoclingOutputFilePath header from values that originate outside the deployment; strip the header from messages arriving from outside before they reach a docling endpoint; ensure consumers which map incoming message headers drop the Camel header namespace. Once fix 4.23.0 is consumed, the outputBaseDirectory endpoint option (unset by default) confines output and rejects out-of-directory/absolute paths.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.4 | N/A | 5.4 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
