CVE-2026-85250
Improper Restriction of XML External Entity Reference vulnerability in Apache Camel XPath component
CVE-2026-85250: Improper Restriction of XML External Entity Reference vulnerability in Apache Camel XPath component. Not in the CISA KEV catalog.
Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.
CVE-2026-85250 at a glance
- CISA KEV
- Not listed (catalog checked )
- Highest advisory severity
- High
- CVSS base score
- 7.5 (Apache), 7.5 (Red Hat)
- Weakness
- CWE-611
- Fixed releases
- Apache: 4.18.5, 4.22.1
- VulniPulse record
- Published · Updated
Scores, vectors, weaknesses and fixed releases are quoted from vendor advisories that cover only CVE-2026-85250; bulletin-wide values are not repeated here.
Is CVE-2026-85250 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-85250 is not in the CISA KEV catalog (checked ) and no tracked advisory for it reports exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-85250?
Upgrade to a fixed release named by the vendor:
- Apache: 4.18.5, 4.22.1
- Upgrade to Apache Camel 4.23.0, which fixes the issue. (Apache)
- Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. (Apache)
Vendor advisory comparison
Apache
1 advisory- Advisory severityHigh7.5
High [CVE-2026-85250] Improper Restriction of XML External Entity Reference vulnerability in Apache Camel XPath component
CVE-2026-85250Source published Source updated
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…
- Affected products in this advisory
- Apache Camel XPath
- Source-reported affected versions
- 4.0.0 before 4.18.5
- 4.19.0 before 4.22.1
- Source-reported fixed versions
- 4.18.5
- 4.22.1
- Mitigation guidance
- 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.
- 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.
Red Hat
1 advisory- Advisory severityHigh7.5
High [CVE-2026-85250] Information disclosure via XML external entity references
CVE-2026-85250Source published Source updated
Information disclosure via XML external entity references. Red Hat rates this important (CVSS 7.5). Weakness: CWE-611. 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; Red Hat build of Apache Camel - HawtIO 4; Red Hat Fuse 7.
- 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
- Red Hat build of Apache Camel - HawtIO 4
- Red Hat Fuse 7
- Source-reported affected versions
- Affected-version details not available in this record.
- Source-reported fixed versions
- No fixed-version detail extracted. This does not mean no fix exists.
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
Browse the latest tracked CVEs or the CVEs listed in CISA KEV.
Android app · Google Play
Turn CVE research into alerts 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.