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

CVE-2026-95628: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Camel Docling component

CVE-2026-95628 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
5.4 (Apache), 5.4 (Red Hat)
Weakness
CWE-22
Fixed releases
  • Apache: 4.18.5, 4.22.2, 4.23.0
  • Red Hat: 4.23.0, 4.22, 4.22.2, 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-95628; each belongs to its advisory, not to every product listed. How records are collected and checked.

How do I fix CVE-2026-95628?

Upgrade to a fixed release named by the vendor:

  • Apache: 4.18.5, 4.22.2, 4.23.0
  • Red Hat: 4.23.0, 4.22, 4.22.2, 4.18, 4.18.5
  • The header belongs to the Camel header namespace, which consumers applying Camel's default header filtering, such as the JMS and Kafka consumers, remove from incoming messages, so the issue is reached where a route forwards externally influenced values into the header or where a consumer maps incoming headers without that filtering. (Apache)
  • Users are recommended to upgrade to version 4.23.0, which fixes the issue. (Apache)
  • 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. (Red Hat)

Vendor advisories for CVE-2026-95628

Apache

1 advisory
  • Advisory severityMedium5.4

    Medium [CVE-2026-95628] Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Camel Docling component

    CVE-2026-95628Source published Source updated

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') 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.2. DoclingProducer builds the command line of the external docling tool and appends to it the custom arguments supplied in the CamelDoclingCustomArguments header, a list of strings whose flags the fix for CVE-2026-40047 restricted to an allowlist. That fix also introduced validatePathSafety to keep path-like argument values inside the intended directory, but the method only looked for relative traversal: it rejected a value containing a traversal sequence such as../ and a value whose normalized form still held a.. element. It never checked whether a value was an absolute path…

    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.2
    Source-reported fixed versions
    • 4.18.5
    • 4.22.2
    • 4.23.0
    Mitigation guidance
    • The header belongs to the Camel header namespace, which consumers applying Camel's default header filtering, such as the JMS and Kafka consumers, remove from incoming messages, so the issue is reached where a route forwards externally influenced values into the header or where a consumer maps incoming headers without that filtering.
    • 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.2.
    • If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5.

    1 more entries in the full advisory.

    Full advisory and evidenceOpen source bulletin

Red Hat

1 advisory
  • Advisory severityMedium5.4

    Medium [CVE-2026-95628] Path traversal via unvalidated absolute paths

    CVE-2026-95628Source published Source updated

    Path traversal via unvalidated absolute paths. Red Hat rates this moderate (CVSS 5.4). Weakness: CWE-22. 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.2

    8 more entries in the full advisory.

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

    1 more entries in the full advisory.

    Mitigation guidance
    • 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.
    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