XML External Entity (XXE) Injection Affecting org.apache.camel:camel-xpath package, versions [4.0.0,4.18.5)[4.19.0,4.22.1)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about XML External Entity (XXE) Injection vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGAPACHECAMEL-21429368
- published22 Oct 2026
- disclosed19 Oct 2026
- creditClaude Security
Introduced: 19 Oct 2026
NewCVE-2026-85250 (opens in a new tab)How to fix?
Upgrade org.apache.camel:camel-xpath to version 4.18.5, 4.22.1 or higher.
Overview
Affected versions of this package are vulnerable to XML External Entity (XXE) Injection via the XPathBuilder in the XPath component. In a route that evaluates externally supplied XML with documentType=InputSource or SAXSource, an unauthenticated external sender can read files accessible to the Camel process and cause it to send requests to attacker-specified hosts by sending a DOCTYPE that declares an external entity; XPathBuilder passes the input to the XPath engine, whose default parser resolves that entity.
Workarounds
- For deployments that cannot upgrade immediately, do not use
documentType=InputSourcefor XPath expressions evaluated over untrusted XML; this prevents attacker-supplied DOCTYPE declarations and external entities from being processed through that vulnerable path.
Details
XXE Injection is a type of attack against an application that parses XML input. XML is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. By default, many XML processors allow specification of an external entity, a URI that is dereferenced and evaluated during XML processing. When an XML document is being parsed, the parser can make a request and include the content at the specified URI inside of the XML document.
Attacks can include disclosing local files, which may contain sensitive data such as passwords or private user data, using file: schemes or relative paths in the system identifier.
For example, below is a sample XML document, containing an XML element- username.
<xml>
<?xml version="1.0" encoding="ISO-8859-1"?>
<username>John</username>
</xml>
An external XML entity - xxe, is defined using a system identifier and present within a DOCTYPE header. These entities can access local or remote content. For example the below code contains an external XML entity that would fetch the content of /etc/passwd and display it to the user rendered by username.
<xml>
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE foo [
<!ENTITY xxe SYSTEM "file:///etc/passwd" >]>
<username>&xxe;</username>
</xml>
Other XXE Injection attacks can access local resources that may not stop returning data, possibly impacting application availability and leading to Denial of Service.