CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NHigh (7.5) in apache camel. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel | from 4.0.0 before 4.18.5 |
| Apache Software Foundation Apache Camel | from 4.19.0 before 4.22.1 |
Red Hat rates this Important.
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.
--- 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)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-xpath | Affected | |
| Red Hat build of Apache Camel for Spring Boot 4 | camel-xpath | Affected | |
| Red Hat build of Apache Camel - HawtIO 4 | camel-xpath | Not affected | |
| Red Hat Fuse 7 | camel-xpath | Out 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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.