Skip to content
VulniPulse
Sign in
Medium 2 vendors · 2 advisories

CVE-2026-78163: 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

CVE-2026-78163 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
5.9 (Apache), 5.9 (Red Hat)
Weakness
CWE-918
Fixed releases
  • Apache: 4.18.5, 4.22.1, 4.23.0
  • Red Hat: 4.23.0, 4.22, 4.22.1, 4.18, 4.18.5
Vendor advisories
2 from Apache, Red Hat
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-78163; each belongs to its advisory, not to every product listed. How records are collected and checked.

How do I fix CVE-2026-78163?

Upgrade to a fixed release named by the vendor:

  • Apache: 4.18.5, 4.22.1, 4.23.0
  • Red Hat: 4.23.0, 4.22, 4.22.1, 4.18, 4.18.5
  • Users are recommended to upgrade to version 4.23.0, which fixes the issue. (Apache)
  • If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.1. (Apache)

Vendor advisories for CVE-2026-78163

Apache

1 advisory
  • Advisory severityMedium5.9

    Medium [CVE-2026-78163] 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

    CVE-2026-78163Source published Source updated

    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…

    Affected products in this advisory
    • Apache Camel Docling
    Source-reported affected versions
    • 4.15.0 before 4.18.5
    • 4.19.0 before 4.22.1
    Source-reported fixed versions
    • 4.18.5
    • 4.22.1
    • 4.23.0
    Mitigation guidance
    • 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.
    • 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.
    Full advisory and evidenceOpen source bulletin

Red Hat

1 advisory
  • Advisory severityMedium5.9

    Medium [CVE-2026-78163] Information disclosure via improper message body prefix handling

    CVE-2026-78163Source published Source updated

    Information disclosure via improper message body prefix handling. Red Hat rates this moderate (CVSS 5.9). Weakness: CWE-918. Affected products named by the advisory: Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Apache Camel for Spring Boot 4.

    Related products — impact not confirmed
    • Red Hat build of Apache Camel 4 for Quarkus 3
    • Red Hat build of Apache Camel for Spring Boot 4
    Source-reported affected versions
    • < 4.15.0
    • < 4.18.5
    • < 4.19.0
    • < 4.22.1

    2 more entries in the full advisory.

    Source-reported fixed versions
    • 4.23.0
    • 4.22
    • 4.22.1
    • 4.18

    1 more entries in the full advisory.

    Mitigation guidance
    No mitigation guidance extracted; consult the source.
    Full advisory and evidenceOpen source bulletin

References

More Apache advisories

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Apache

iPhone and Android apps · New on the App Store

Get alerts for new CVEs on your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Download on the App StoreGet CVE alerts on AndroidSee app features