CVE-2026-85250

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.

• CWE-611

• https://camel.apache.org/security/CVE-2026-85250.htmlMitigation, Patch, Vendor Advisory
• https://github.com/apache/camel/pull/25683Issue Tracking, Patch
• https://github.com/apache/camel/pull/25940Issue Tracking, Patch
• https://github.com/apache/camel/pull/25942Issue Tracking, Patch
• https://issues.apache.org/jira/browse/CAMEL-24475Issue Tracking, Patch

Published

Oct 19, 2026

Last Modified

Nov 3, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-85245Exposure of Data Element to Wrong Session vulnerability in A…5.9
• CVE-2026-85246Generation of Error Message Containing Sensitive Information…5.3
• CVE-2026-85247Improper Certificate Validation vulnerability in Apache Came…5.9
• CVE-2026-85248Concurrent Execution using Shared Resource with Improper Syn…5.9
• CVE-2026-85249Improper Input Validation vulnerability in Apache Camel Tika…6.5
• CVE-2026-8525Heap buffer overflow in ANGLE in Google Chrome on Mac prior …8.3
• CVE-2026-85251Exposure of Sensitive Information to an Unauthorized Actor v…7.5
• CVE-2026-85254Improper Handling of Case Sensitivity vulnerability in Apach…6.5
• CVE-2026-85257Generation of Error Message Containing Sensitive Information…5.3
• CVE-2026-8526Out of bounds write in WebRTC in Google Chrome prior to 148.…8.8
• CVE-2026-85260Insertion of Sensitive Information into Log File vulnerabili…5.5
• CVE-2026-85267A Cross-Site WebSocket Hijacking vulnerability in Cloud Shel…8.7