cve.bz

CVE-2026-85250 apache camel

7.5 highEPSS 0.7%Fix available

High (7.5) in apache camel. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
Improper Restriction of XML External Entity Reference vulnerability in Apache Camel XPath component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. With documentType set to InputSource, XPathBuilder handed the payload straight to javax.xml.xpath, which builds a DocumentBuilder of its own using the JDK defaults. The hardening applied to Camel's default document type was therefore bypassed: a DOCTYPE declaration that is refused on the default type was accepted here, and the external entity it declared was resolved and expanded into the evaluated document. An external sender whose XML reaches such an expression could read files readable by the Camel process and cause the process to issue requests to hosts it names. The two document types disagreeing on parser configuration is what made this reachable, since a deployment choosing InputSource for streaming reasons had no indication it was also choosing a weaker parser. Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The InputSource document type now goes through the same hardened parser as the default type, so a DOCTYPE is refused. Note that it also shares that type's documented escape hatch: the same DocumentBuilderFactory system properties that relax the default type relax this one, so a deployment that has set them remains unprotected by design. For deployments that cannot upgrade immediately, do not use documentType=InputSource on expressions evaluated over untrusted XML; the default document type already refuses a DOCTYPE.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.7% (unchanged from 0.7% a week ago) estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-611 Improper Restriction of XML External Entity Reference
OWASP Top 10
A02:2025 Security Misconfiguration
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-85250 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-85250?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-85250?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-85250 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-85250

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-85250](https://cve.bz/cve/badge/CVE-2026-85250.svg)](https://cve.bz/cve/CVE-2026-85250)

HTML:

<a href="https://cve.bz/cve/CVE-2026-85250"><img src="https://cve.bz/cve/badge/CVE-2026-85250.svg" alt="CVE-2026-85250"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.0.0 before 4.18.5
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.22.1

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because remote, unauthenticated attackers can exploit it over the network to read arbitrary local files accessible to the application or initiate unauthorized outbound requests. While default XPath configurations in Red Hat build of Apache Camel enforce secure XML processing and disallow DOCTYPE declarations, deployments explicitly setting the documentType option to InputSource bypass these protections. Systems are exposed only when routes parse untrusted external XML payloads using this specific streaming configuration.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-10-20) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to route InputSource payloads through Camel's hardened DocumentBuilderFactory to refuse DOCTYPE declarations instead of unhardened JDK defaults: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Xpath builds), which route InputSource instances through toHardenedDocument using Camel's hardened DocumentBuilderFactory to refuse DOCTYPE declarations by default, closing all 2 injection vectors (crafted XML containing DOCTYPE entity references for local file disclosure, crafted XML containing external system identifiers triggering outbound HTTP requests (SSRF)). Until patched, this is a concern on deployments evaluating XPath expressions with documentType set to InputSource over untrusted XML, so avoid using documentType=InputSource on expressions evaluated over untrusted XML and ensure DocumentBuilderFactory system properties do not relax parser hardening. As a compensating measure, block outbound network connections from the application host to contain SSRF vectors triggered by external entity system identifiers and deploy runtime detection to alert on anomalous local sensitive file reads and unexpected outbound network connections initiated by the application process. These controls limit blast radius and contain exploitation, but they do not fix the underlying XML external entity injection flaw — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1317 XML External Entity Prevention (Secure XML Parser Configuration) (high)

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3camel-xpathAffected
Red Hat build of Apache Camel for Spring Boot 4camel-xpathAffected
Red Hat build of Apache Camel - HawtIO 4camel-xpathNot affected
Red Hat Fuse 7camel-xpathOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-85250.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-85250 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-85250 — Apache Camel camel-xpath XML external entity processing via documentType=InputSource (CWE-611); Spring Boot…

Attack patterns (CAPEC)

  • CAPEC-221 Data Serialization External Entities Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON