CVE-2026-88901: CWE-611 Improper Restriction of XML External Entity Reference in Apache Software Foundation Apache Camel
Description
Improper Restriction of XML External Entity Reference vulnerability in Apache Camel. This issue affects Apache Camel: from 4.7.0 before 4.18.5, from 4.19.0 before 4.22.1. Improper Restriction of XML External Entity Reference in the Smooks component (camel-smooks) in Apache Camel allows an attacker who supplies the XML message body to read local files or issue requests to internal network locations via an external entity declaration in that body. This issue affects Apache Camel: from 4.7.0 before 4.18.5, from 4.19.0 before 4.22.1. The Smooks data format (.unmarshal().smooks(...)) and the Smooks component (smooks:) parse the incoming XML body with the reader Smooks resolves by default, which is the Woodstox SAX parser. That reader resolves external general and parameter entities and loads external DTDs, and camel-smooks applied none of the parser hardening that the other Camel XML components apply. A DOCTYPE with an external subset, or an external general entity, declared in the XML document is therefore resolved and expanded while the body is unmarshalled, and the resolved content is bound into the unmarshalled result and returned on InOut routes. An external sender whose XML reaches a camel-smooks data format or endpoint could therefore read files readable by the Camel process and cause the process to issue requests to hosts the document names. No non-default option is required, since resolving external entities was the default behaviour. Configurations that declare their own reader - EDI, CSV, JSON, or a custom reader - do not use the XML reader and are not affected. Users are recommended to upgrade to version 4.18.5, 4.22.1 or 4.23.0, which fixes the issue. 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. camel-smooks now parses the XML body with a javax.xml.parsers.DocumentBuilder that does not resolve external general or parameter entities and does not load external DTDs, and hands Smooks the resulting document, matching the secure XML processing configuration used by org.apache.camel.converter.jaxp.XmlConverter and the other Camel XML components. This hardening is applied only when the Smooks configuration parses XML with its default reader, so EDI, CSV, JSON and custom-reader configurations, and the marshalling direction, are unchanged. A new allowExternalEntities option, disabled by default, restores the previous behaviour for trusted legacy configurations that rely on external entity resolution. The camel-4.14.x releases stream and earlier reached end of life before this issue was resolved and will not receive a fix, so deployments on those lines must move to a supported release. For deployments that cannot upgrade immediately, do not apply camel-smooks to XML received from untrusted senders.
CVSS v3.1
Score 8.2high
Affected software
Apache Software Foundation
Apache Camel
pkg:maven/Apache Software Foundation/org.apache.camel:camel-smooksRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Apache Camel's Smooks component (camel-smooks) improperly restricts XML External Entity references, allowing attackers who control the XML message body to read local files or send requests to internal network locations. This occurs because the default Woodstox SAX parser resolves external general and parameter entities and loads external DTDs without parser hardening. The vulnerability affects Apache Camel versions >=4.7.0 <4.18.5 and >=4.19.0 <4.22.1. The issue is fixed in versions 4.18.5, 4.22.1, and 4.23.0 by switching to a DocumentBuilder that does not resolve external entities or load external DTDs. A new allowExternalEntities option, disabled by default, allows legacy behavior for trusted configurations. Versions 4.14.x and earlier are end-of-life and will not receive fixes. Users unable to upgrade immediately should avoid applying camel-smooks to XML from untrusted sources.
Potential Impact
An attacker who can supply XML to the vulnerable camel-smooks component can exploit the XXE vulnerability to read local files accessible by the Camel process or cause the process to issue network requests to internal hosts. This can lead to information disclosure and limited denial of service. The CVSS 3.1 score is 8.2 (high severity), reflecting network attack vector, low complexity, no privileges required, no user interaction, high confidentiality impact, no integrity impact, and low availability impact.
Mitigation Recommendations
Upgrade Apache Camel to version 4.18.5, 4.22.1, or 4.23.0, where the vulnerability is fixed by disabling external entity resolution by default in camel-smooks. For users on unsupported versions (4.14.x and earlier), immediate upgrade is recommended as no fixes will be provided. If upgrading is not immediately possible, do not apply camel-smooks to XML input from untrusted sources. The new allowExternalEntities option is disabled by default and should remain so unless legacy trusted configurations require it.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-09-10T11:43:50.047Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ad5f5a02cdf04f65643555d
Added to database: 10/19/2026, 10:49:04 UTC
Last enriched: 10/19/2026, 11:03:38 UTC
Last updated: 10/19/2026, 15:04:07 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.