CVE-2026-95628
Apache Camel: Camel-Docling Custom CLI Argument Path Validation Does Not Reject Absolute Paths (Incomplete Fix of CVE-2026-40047)
02 Description
Apache Camel: Camel-Docling Custom CLI Argument Path Validation Does Not Reject Absolute Paths (Incomplete Fix of CVE-2026-40047)
03 Exploitation and scoring
- Exploitation
- Assessed, none found. CISA's assessment recorded neither public exploit code nor evidence of exploitation when it was made.
- SSVC decision
- ExploitationnoneCISA recorded no public exploit code and no evidence of exploitation.
- AutomatablenoAt least one step from reconnaissance to exploitation cannot be reliably automated.
- Technical ImpactpartialSuccessful exploitation gives limited control of the vulnerable component.
- EPSS probability
- 0.33% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 26.7% of scored records. A rank, not a probability.
- NVD base score
- 5.4 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- NVD analysis status
- Awaiting Analysis. NVD last modified this record on 2026-10-26.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2026-10-26 08:48Z3 DAYS AGO
- Last updated
- 2026-10-26 14:35Z3 DAYS AGO
- Reserved
- 2026-09-22
- Assigning CNA
- apache
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 5.4)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- Weaknesses
- CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')Base
- Data version
- 5.2
- Document digest
- 37a07562be8756e8487538e65af8edfaa4502c6c93f1db595887cdce5e363c4e
05 Affected products
06 References
- camel.apache.orgApache Camel Security Advisory - CVE-2026-95628https://camel.apache.org/security/CVE-2026-95628.html
- issues.apache.orgCAMEL-24893https://issues.apache.org/jira/browse/CAMEL-24893
- github.comFix on main, released in 4.23.0 (commit fd3bc8e73613f3aec691044ed07869ef79c1bf2f)https://github.com/apache/camel/pull/26738
- github.comBackport to camel-4.22.x for 4.22.2 (commit e9233c37c6127221157ac0901fb74250c5d24e98)https://github.com/apache/camel/pull/26743
- github.comBackport to camel-4.18.x, released in 4.18.5 (commit 59d30af17064320073e17cfb516be60d096bb979)https://github.com/apache/camel/pull/26744
- camel.apache.orgCVE-2026-40047, the custom CLI argument validation issue whose fix this completeshttps://camel.apache.org/security/CVE-2026-40047.html
- camel.apache.orgCVE-2026-78163, a distinct input-source issue in the same producerhttps://camel.apache.org/security/CVE-2026-78163.html
07 Remediation
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.22.x stream should upgrade to 4.22.2 and users on the 4.18.x stream should upgrade to 4.18.5. The validatePathSafety helper now also rejects a path-like custom-argument value that is an absolute path, whether it is given as a separate list element or attached to its flag, so every path-valued flag on the allowlist is covered; a relative value without traversal segments is still accepted. The 4.15.x to 4.17.x and 4.19.x to 4.21.x release lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release.