On this page
CVE Details
- Protection status: Protected by Atomicorp rules · About protection statuses
- CVE: CVE-2026-78163
- Name: Apache Camel: Camel-Docling Unvalidated Message Body Input Source Enables Server-Side Request Forgery and Local File Dis
- Severity: Medium
- CVSS: 5.9 (v3.1) (Medium)
- CVSS version: 3.1
- CVSS source: apache CNA
- CVSS vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N- Attack vector: Network
- Attack complexity: High
- Privileges required: None
- User interaction: None
- Scope: Unchanged
- Confidentiality impact: High
- Integrity impact: None
- Availability impact: None
- CWE: CWE-22 — Improper Limitation of a Pathname to a Restricted Directory, CWE-200 — Exposure of Sensitive Information to an Unauthorized Actor, CWE-918 — Server-Side Request Forgery
- Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-116 (opens in a new tab) , CAPEC-126 (opens in a new tab) , CAPEC-13 (opens in a new tab) , CAPEC-169 (opens in a new tab) , CAPEC-22 (opens in a new tab) , CAPEC-224 (opens in a new tab) , CAPEC-285 (opens in a new tab) , CAPEC-287 (opens in a new tab) , CAPEC-290 (opens in a new tab) , CAPEC-291 (opens in a new tab) , CAPEC-292 (opens in a new tab) , CAPEC-293 (opens in a new tab) , CAPEC-294 (opens in a new tab) , CAPEC-295 (opens in a new tab) , CAPEC-296 (opens in a new tab) , CAPEC-297 (opens in a new tab) , CAPEC-298 (opens in a new tab) , CAPEC-299 (opens in a new tab) , CAPEC-300 (opens in a new tab) , CAPEC-301 (opens in a new tab) , CAPEC-302 (opens in a new tab) , CAPEC-303 (opens in a new tab) , CAPEC-304 (opens in a new tab) , CAPEC-305 (opens in a new tab) , CAPEC-306 (opens in a new tab) , CAPEC-307 (opens in a new tab) , CAPEC-308 (opens in a new tab) , CAPEC-309 (opens in a new tab) , CAPEC-310 (opens in a new tab) , CAPEC-312 (opens in a new tab) , CAPEC-313 (opens in a new tab) , CAPEC-317 (opens in a new tab) , CAPEC-318 (opens in a new tab) , CAPEC-319 (opens in a new tab) , CAPEC-320 (opens in a new tab) , CAPEC-321 (opens in a new tab) , CAPEC-322 (opens in a new tab) , CAPEC-323 (opens in a new tab) , CAPEC-324 (opens in a new tab) , CAPEC-325 (opens in a new tab) , CAPEC-326 (opens in a new tab) , CAPEC-327 (opens in a new tab) , CAPEC-328 (opens in a new tab) , CAPEC-329 (opens in a new tab) , CAPEC-330 (opens in a new tab) , CAPEC-472 (opens in a new tab) , CAPEC-497 (opens in a new tab) , CAPEC-508 (opens in a new tab) , CAPEC-573 (opens in a new tab) , CAPEC-574 (opens in a new tab) , CAPEC-575 (opens in a new tab) , CAPEC-576 (opens in a new tab) , CAPEC-577 (opens in a new tab) , CAPEC-59 (opens in a new tab) , CAPEC-60 (opens in a new tab) , CAPEC-616 (opens in a new tab) , CAPEC-64 (opens in a new tab) , CAPEC-643 (opens in a new tab) , CAPEC-646 (opens in a new tab) , CAPEC-651 (opens in a new tab) , CAPEC-664 (opens in a new tab) , CAPEC-76 (opens in a new tab) , CAPEC-78 (opens in a new tab) , CAPEC-79 (opens in a new tab)
- Vendor: Apache Software Foundation
- Vulnerable product: Apache Camel
- CVE published: 2026-10-19
- CVE last modified: 2026-10-19
- EPSS: 0.0046; 40.8th percentile as of 2026-11-20 (FIRST (opens in a new tab) )
- Latest Update: 2026-11-10
- Selected Rule IDs observed: 390719
- Matching rules: 1; rules with blocking actions: 1
- Would-block Rule IDs: 390719
- Request surfaces inspected: Request headers
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data
CVSS assessments
CVSS v3.1 · security@apache.org
- Base score: 5.9
- Base severity: MEDIUM
- Exploitability subscore: 2.2
- Impact subscore: 3.6
- Assessment type: Secondary
- Source identifier: security@apache.org
- Full vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N- Attack vector: Network
- Attack complexity: High
- Privileges required: None
- User interaction: None
- Scope: Unchanged
- Confidentiality impact: High
- Integrity impact: None
- Availability impact: None
- Exploit maturity: Not scored
Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.
Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)
CISA SSVC assessments
These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.
- Provider: CISA ADP
- Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
- SSVC version: 2.0.3
- Role: CISA Coordinator
- Assessment timestamp: 2026-10-19T18:47:11.066796Z
- Exploitation: none
- Automatable: no
- Technical Impact: partial
- Source: CISA ADP in the CVE record (opens in a new tab)
Vulnerable CPE configurations
No vulnerable CPE configurations are supplied in the current NVD record. See the affected-product information and vendor guidance on this page.
Vulnerability Description
Server-Side Request Forgery (SSRF), Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’) and Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Camel Docling component.
This issue affects Apache Camel: from 4.15.0 before 4.18.5, from 4.19.0 before 4.22.1.
DoclingProducer decided what a String message body meant by inspecting its prefix. A body starting with http:// or https:// was handed to Docling as a remote URL to fetch, a body starting with / or containing a backslash was read from the local filesystem, and anything else was written to a temporary file and converted as document content. The mode was chosen implicitly and no endpoint option allowed a route author to pin the component to a single interpretation, so a route that means convert whatever text arrives in the body silently became a fetcher of remote resources or a reader of local files whenever the text happened to begin with one of those prefixes. The only guard applied to the derived value was a size check, and that check was wrapped in an existence test, so a path that resolved to nothing, or to a pseudo-file reporting a size of zero, passed without being checked at all. Five call sites reached the two sinks: the CLI mode appended the value as the final positional argument of the docling subprocess, and the docling-serve mode passed it either to HttpSource for the backend to fetch or to Files.readAllBytes so that the content could be base64-encoded and uploaded. Because the exchange body is never filtered by a HeaderFilterStrategy, unlike the Camel header namespace, a sender able to place text in a message that a route forwards into a docling endpoint could reach both sinks without any opt-in from the deployment.
Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.1. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The 4.14.x releases stream and earlier reached end of life before this issue was resolved and will not receive a fix, so deployments on those lines must move to a supported release. For deployments that cannot upgrade immediately, do not route message bodies that originate outside the deployment into a docling endpoint, and pass the document through a typed body such as File, byte[] or InputStream, or through the CamelDoclingInputFilePath header, so that the body is never subject to prefix interpretation.
Recommended Actions
Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (390719 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.
Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.
- Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.18.5.
- Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.22.1.
- Versions reported unaffected: Apache Software Foundation Apache Camel version 4.18.5.
- Versions reported unaffected: Apache Software Foundation Apache Camel version 4.22.1.
- Versions reported unaffected: Apache Software Foundation Apache Camel version 4.23.0.
- Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.18.5 or later.
- Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.22.1 or later.
- CNA guidance source: apache (opens in a new tab)
- Vendor recommendation: Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.22.x stream should upgrade to 4.22.1 and users on the 4.18.x stream should upgrade to 4.18.5. The 4.14.x stream and earlier reached end of life before this issue was resolved and will not receive a fix.
- Vendor workaround: Do not route message bodies originating outside the deployment into a docling endpoint. Pass the document through a typed body such as File, byte[] or InputStream, or through the CamelDoclingInputFilePath header, so that the body is not subject to prefix interpretation.
Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.
Research Notes
Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.
Public Vulnerability References
- NVD (opens in a new tab)
- CVE Record (opens in a new tab)
- CVE authority reference: https://camel.apache.org/security/CVE-2026-78163.html (opens in a new tab)
- CVE authority reference: https://github.com/apache/camel/pull/25596 (opens in a new tab)
- CVE authority reference: https://github.com/apache/camel/pull/25733 (opens in a new tab)
- CVE authority reference: https://github.com/apache/camel/pull/25744 (opens in a new tab)
- CVE authority reference: https://issues.apache.org/jira/browse/CAMEL-24422 (opens in a new tab)
Test or Research Source
- Source: Atomicorp AI Research Framework
- Tags: cve, derived, ssrf, waf-probe
Research Note Context
This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.
Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.
Learn More
Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.
Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:
- Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
- Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
- Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
- Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
- Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.
For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .