# CVE-2026-85250: Apache Camel: Camel-XPath XML External Entity Processing and File Disclosure via the documentType=InputSource Option


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-x9f8-58m2-93q2

## What is CVE-2026-85250?

CVE-2026-85250 is a high-severity vulnerability in Apache Camel, published on 19 Oct 2026. 

### Official description

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.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2026-85250?


## How do I fix CVE-2026-85250?

No fix has been published for CVE-2026-85250 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85250 being exploited?

There is no known exploitation of CVE-2026-85250 in the wild and no public exploit code.

Public exploit code:

- Reproducer for CVE-2026-85250 — Apache Camel camel-xpath XML external entity processing via documentType=InputSource (CWE-611); Spring Boot + Quarkus, affected vs fixed (github_poc): https://github.com/oscerd/CVE-2026-85250

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85250 and fix it if it is affected.

What it is: CVE-2026-85250 is a high-severity vulnerability in Apache Camel, published on 19 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-85250 in the wild and no public exploit code.

Affected product: Apache Camel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85250/ (Markdown: https://insights.sbomify.com/CVE-2026-85250/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85250
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85250
- OSV: https://osv.dev/vulnerability/CVE-2026-85250

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85250/
Summaries are generated and may contain mistakes; the official description above is the record.