CVE-2026-95628
Description
A flaw was found in the Apache Camel Docling component. A remote attacker able to influence message headers can exploit this path traversal vulnerability by providing absolute paths in custom command-line arguments. Because the component only checks for relative traversal sequences, absolute paths bypass the restriction to the intended working directory. This allows the external processing tool to access unintended file system locations, potentially compromising data integrity or causing a Denial of Service (DoS).
Statement
Red Hat has evaluated this vulnerability as having a Moderate severity because exploitation requires non-default routing conditions where externally influenced values are explicitly mapped into internal message headers. Standard Camel consumers, such as those for JMS and Kafka, strip headers within the Camel namespace by default, significantly reducing accidental exposure. Furthermore, any unauthorized directory access executed by the Docling CLI process is strictly bounded by the operating system permissions assigned to the running Camel process.
Mitigation
Upgrade to camel-docling 4.18.5 (4.18.x stream) / 4.22.2 / 4.23.0 when available in product streams; as a workaround, avoid forwarding externally influenced values into the CamelDoclingCustomArguments header and rely on consumers that strip Camel-namespace headers (JMS, Kafka defaults); the fixed validatePathSafety rejects absolute path-like values with IllegalArgumentException.
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.
