# CVE-2026-85250: Apache Camel XXE vulnerability in XPath component

Source: https://junglewise.ai/threats/cve-2026-85250-improper-restriction-of-xml-external-entity-reference  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-19. Updated: 2026-10-19  
License: CC BY 4.0 with a link back

CVE-2026-85250 · Severity: high · CVSS 7.5 · Published 2026-10-19

Apache Camel is an integration framework that processes XML messages as part of data pipelines. An attacker can exploit a weakness in the XPath component's XML parsing to read files from the server or cause it to make requests to external hosts, bypassing Camel's normal security hardening when using InputSource document type.

Technologies: [Apache Camel](https://junglewise.ai/threats/technologies/camel). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-85250 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-85250 being exploited in the wild.

**How severe is CVE-2026-85250?** High severity, with a CVSS score of 7.5, published 19 October 2026.

**Which products and versions are affected?** Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1.

**Is there a fix for CVE-2026-85250?** Yes: fixed in Apache Camel 4.23.0, 4.18.5 (LTS), 4.22.1 (LTS). Until then: Do not use documentType=InputSource on XPath expressions evaluated over untrusted XML; use the default document type instead, which already refuses DOCTYPE declarations. Alternatively, set DocumentBuilderFactory system properties to disable external entity resolution if immediate upgrade is not possible. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-85250 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-85250?** Check whether you run Apache Camel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Apache Camel 4.23.0, 4.18.5 (LTS), 4.22.1 (LTS)

Do not use documentType=InputSource on XPath expressions evaluated over untrusted XML; use the default document type instead, which already refuses DOCTYPE declarations. Alternatively, set DocumentBuilderFactory system properties to disable external entity resolution if immediate upgrade is not possible.

## Technical details

An XML External Entity (XXE) vulnerability exists in Apache Camel's XPathBuilder when documentType is set to InputSource. The component bypasses Camel's hardened document parser and uses the JDK's default DocumentBuilder configuration, which allows DOCTYPE declarations and external entity expansion. An attacker can send malicious XML containing entity declarations to read arbitrary files or trigger outbound requests to attacker-controlled hosts.

## Affected products

- Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1

## Timeline

- 2026-10-19: disclosed

## Related threats

- [Apache Camel SSRF in A2A webhook validator](https://junglewise.ai/threats/cve-2026-71569-server-side-request-forgery-ssrf-vulnerability-in-apache-camel)
- [Apache Camel OAuth component cache containing sensitive information](https://junglewise.ai/threats/cve-2026-94386-use-of-cache-containing-sensitive-information-vulnerability-in)
- [Apache Camel Saxon component XXE in XQuery evaluation](https://junglewise.ai/threats/cve-2026-90885-improper-restriction-of-xml-external-entity-reference)
- [Apache Camel AWS2-S3 expression language injection in key handling](https://junglewise.ai/threats/cve-2026-95664-improper-neutralization-of-special-elements-used-in-an-expression)
- [Apache Camel Keycloak security policy token expiration bypass](https://junglewise.ai/threats/cve-2026-95663-insufficient-session-expiration-vulnerability-in-apache-camel)