CVSS 3.1
8.2 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:LHigh (8.2) in apache software foundation apache camel. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:LExplain CVE-2026-88901 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-88901?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-88901?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-88901 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel | from 4.7.0 before 4.18.5 |
| Apache Software Foundation Apache Camel | from 4.19.0 before 4.22.1 |
Red Hat rates this Important.
Red Hat rates this issue as Important because remote, unauthenticated attackers can leverage default XML parsing behavior in camel-smooks to exfiltrate host filesystem data and trigger server-side request forgery. In typical Red Hat build of Apache Camel deployments, exploitation is possible without elevated privileges if an integration route accepts untrusted XML payloads for transformation via the Smooks component or data format. Routes that do not process external XML input, or that configure non-XML readers such as CSV, JSON, or EDI, are not exposed to this flaw.
--- CME Mitigation Guidance (2026-10-20) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to disable external entity resolution and external DTD processing in the XML parser before handing input to Smooks: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Smooks builds), which pre-parse XML using a hardened DocumentBuilder that disables external entities and external DTD loading before passing to Smooks, and add an allowExternalEntities option defaulting to false, closing all 2 injection vectors (external general entity declaration, DOCTYPE external subset resolution). Until patched, this is only a concern on Camel routes processing XML messages using camel-smooks with the default XML reader — Configurations using custom readers such as EDI, CSV, or JSON, and the marshalling direction are unaffected — so do not apply camel-smooks endpoints or data formats to XML messages received from untrusted senders. As a compensating measure, restrict outbound network egress from the Camel host process to contain unauthorized SSRF requests and internal network scanning. These controls limit blast radius and contain exploitation, but they do not fix the underlying XML external entity injection defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1317 XML External Entity Prevention (Secure XML Parser Configuration) (high)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-smooks | Affected | |
| Red Hat build of Apache Camel for Spring Boot 4 | camel-smooks | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-88901.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.