HighPublic exploitVulnerability

CVE-2026-85250

XXE in Apache Camel XPath InputSource processing

Published Oct 19, 2026 · Updated today

Trending this weekNot trendingOutside this week’s top 100

Mention activity · 30 days

3 mentions · peak 2 in a dayToday

CVSS7.5High · v3.1

EPSS0.56%46th percentile

CISA KEVNoNot listed

In the wildNonePublic exploit, no exploitation reported

Vendor: Apache Software Foundation

IdentifiersCVE-2026-85250CWE-611 · Improper Restriction of XML…

CVE-2026-85250 is an XML external entity vulnerability in the Apache Camel XPath component affecting versions 4.0.0 before 4.18.5 and 4.19.0 before 4.22.1. When documentType=InputSource is configured, XPathBuilder passes XML directly to javax.xml.xpath, which creates its own DocumentBuilder using JDK defaults rather than Camel's hardened parser. This bypass allows DOCTYPE declarations and external entity resolution that the default document type rejects. Attacker-controlled XML reaching an affected expression can expose files readable by the Camel process and trigger requests to attacker-specified hosts.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.

Check your exposure

Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can disclose local files accessible to the Camel process and cause server-side request forgery to attacker-selected destinations, including reachable internal hosts. File access is constrained by the process's permissions, and outbound requests are constrained by its network access.

Mitigation

If you can’t patch tonight, do this now.

Until an upgrade is possible, avoid documentType=InputSource for XPath expressions evaluated over untrusted XML. Use the default document type, which rejects DOCTYPE declarations under its hardened configuration. Remove DocumentBuilderFactory system-property overrides that relax these protections.

Remediation

Patch, then assume compromise.

Upgrade to Apache Camel 4.23.0, or to 4.18.5 on the 4.18.x LTS stream or 4.22.1 on the 4.22.x LTS stream. These releases route InputSource processing through the same hardened parser used by the default document type, rejecting DOCTYPE declarations. Ensure DocumentBuilderFactory system properties do not explicitly relax parser protections, because these overrides also weaken the patched InputSource processing path.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →

CVE-2026-85250The repository contains two standalone Java reproducer applications, not modules for an exploitation framework. Its 17 files comprise seven Java sources, two Maven POMs, two Dockerfiles, two Docker Compose definitions, two application configuration files, a README, and .gitignore. The Spring Boot module uses Spring Boot 3.5.13 and Camel 4.22.0; the Quarkus module uses Quarkus/Camel Quarkus 3.29.0, documented as bundling Camel 4.15.0. Both containers use a Java 17 runtime and publish port 8080. Each module has a startup component that writes a harmless marker file, an HTTP attack controller/resource, and a Camel XPath route. Spring Boot additionally includes an explicit main application class. Calling GET /exploit/attack constructs a fixed DOCTYPE/external-entity XML document referencing the marker file and submits it as an InputStream to direct:eval. The route evaluates /test/text() with documentType=InputSource. On the claimed vulnerable parser path, entity expansion places the file contents in the XPath result, which is returned to the HTTP caller. This is an active, hardcoded file-disclosure demonstration rather than a version-only detection script; it does not implement command execution, persistence, arbitrary target scanning, or an outbound HTTP SSRF payload. The README attributes the behavior to CWE-611 and CVE-2026-85250, describing a bypass of Camel's usual XML parser hardening when InputSource is passed to the JDK XPath implementation. It documents patched controls using Camel 4.22.1 and Camel Quarkus/Quarkus 3.40.0, and also lists fixed Camel releases 4.18.5 and 4.23.0. Those advisory and version assertions were not independently verified, and no application was executed during this static analysis. The code labels every evaluation exception as a patched outcome without checking that DOCTYPE rejection caused it, so an error alone is not reliable proof of remediation. No external callback or command-and-control destination is present; README advisory links and Maven schema URLs are documentation/build metadata rather than exploit callbacks. The original repository URL, analyzed git reference, and archive size were not supplied; their metadata fields use empty strings and zero as unknown-value placeholders.oscerd · Disclosed Oct 19, 2026 · java · webOperational

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

Apache Software FoundationCamelapplication

External references

References

MITRE CVEcve.org · CVE-2026-85250 NVDnvd.nist.gov/vuln/detail/CVE-2026-85250 MITRE CWE · CWE-611Improper Restriction of XML External Entity…camel.apache.orgcamel.apache.org/security/CVE-2026-85250.html github.comgithub.com/apache/camel/pull/25683 github.comgithub.com/apache/camel/pull/25940 github.comgithub.com/apache/camel/pull/25942 issues.apache.orgissues.apache.org/jira/browse/CAMEL-24475

Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →

cyber security newsNews · Oct 27, 2026Apache Camel Fixes Multiple Vulnerabilities Including High-Severity XXE One’sAn XML external entity vulnerability in Camel-XPath allows XML declarations normally blocked by the default document type to be accepted through the InputSource processing path. Fixes are available in versions 4.18.5, 4.22.1, and 4.23.0.Read more ↗cryptika blogNews · Oct 27, 2026Apache Camel Fixes Multiple Vulnerabilities Including High-Severity XXE One’s | Cryptika CybersecurityA high-severity XML external entity vulnerability in Camel-XPath arises when the InputSource processing path uses an engine-created parser with JDK defaults, accepting XML declarations blocked by the default document type. Fixed in versions 4.18.5, 4.22.1, and 4.23.0.Read more ↗ghsa syntheticNews · Oct 19, 2026GHSA-x9f8-58m2-93q2An XML external entity vulnerability in Apache Camel's XPath component bypasses parser hardening when documentType=InputSource is used. XPathBuilder passes XML to javax.xml.xpath, which creates a parser using JDK defaults instead of Camel's hardened configuration. An external sender whose untrusted XML reaches an affected expression can use external entities to read files accessible to the Camel process and trigger requests to attacker-specified hosts. Fixed releases are 4.18.5, 4.22.1, and 4.23.0. Until upgrading, avoid documentType=InputSource for untrusted XML and use the default document type, which rejects DOCTYPE declarations. System properties that explicitly relax DocumentBuilderFactory hardening can leave deployments unprotected even after upgrading.Read more ↗

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.

Check your exposure

Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.

Start Free Trial Open in App ↗

Exposure mappingQuery your assets running an affected version, and investigate the blast radius.

Threat actor evidenceEvery report linking this CVE to a named adversary.

Associated malwareMalware families linked to this CVE, with evidence and IOCs.

Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.

Social activityCommunity discussion across Reddit, Mastodon, and other social sources.