CVE-2026-88901: Apache Camel: Camel-Smooks XML External Entity Processing, external entities resolved by default
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camel camel-smooksto a version that resolves this vulnerability.Fixed in 4.23.0 - Compensating control
For deployments that cannot upgrade immediately, do not apply camel-smooks to XML received from untrusted senders.
Event History
Frequently Asked Questions
Which Camel integrations are affected?
Applications using camel-smooks through the Smooks data format, such as .unmarshal().smooks(...), or through the smooks: component are affected when they process incoming XML. Affected releases are 4.7.0 through before 4.18.5 and 4.19.0 through before 4.22.1.
Does exploitation require a non-default XML parser configuration?
No. camel-smooks uses the Woodstox SAX parser selected by Smooks by default, and the affected integration did not apply the XML parser hardening used by other Camel XML components. That parser resolves external general entities, parameter entities, and external DTDs.
What must an attacker be able to do?
An attacker must be able to supply an XML message body that reaches a vulnerable camel-smooks unmarshalling path. A DOCTYPE containing an external subset or an external general entity can then be resolved during unmarshalling.
What is the practical impact for InOut routes?
Resolved external content can include local file contents or responses from internal network locations. On InOut routes, that content is bound into the unmarshalled result and returned, which can expose the resolved data to the sender.
Which fixed releases should be used?
Upgrade to Apache Camel 4.18.5 or later on the 4.18 release line, or 4.22.1 or later on the 4.22 release line.