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.
Published: 2026-10-19
Score: 8.2 High
EPSS: n/a
KEV: No
Impact: XML External Entity injection resulting in local file disclosure and internal network requests
Action: Immediate Patch
AI Analysis

Impact

The vulnerability occurs in the Smooks component of Apache Camel when it parses incoming XML using its default Woodstox SAX parser, which automatically resolves external general and parameter entities and loads external DTDs. An attacker can embed a DOCTYPE or external entity declaration in the XML payload to cause the Camel process to read arbitrary local files or send requests to internal network hosts. The files that can be read are those accessible by the Camel runtime and the injected content is returned in InOut routes, exposing sensitive data or providing a foothold for further attacks.

Affected Systems

Versions 4.7.0 through 4.18.4, 4.19.0 through 4.22.0 of Apache Camel are affected. Users on the 4.18.x LTS stream should move to 4.18.5, on the 4.22.x LTS stream to 4.22.1, and all users should upgrade to 4.23.0 or newer. The 4.14.x and earlier releases are out of support and require moving to a supported release line.

Risk and Exploitability

The CVSS score of 8.2 indicates high severity. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is an untrusted sender transmitting XML that is processed by the Smooks data format or SMooks endpoint without any remediation in place. The lack of a available EPSS score suggests no published exploitation data yet, but the high CVSS and the ability to read local files or trigger internal traffic make the risk significant. The default behavior of the vulnerable parser implies that no special configuration changes are needed by an attacker – simply sending crafted XML to a Smooks endpoint would be sufficient.

Generated by OpenCVE AI on October 19, 2026 at 12:50 UTC.

Remediation

Vendor Solution

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.


Vendor Workaround

Do not apply the Smooks data format or the Smooks component to XML received from untrusted senders. 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.


OpenCVE Recommended Actions

  • Upgrade to Apache Camel 4.23.0, or to 4.18.5 on the 4.18.x LTS stream and to 4.22.1 on the 4.22.x LTS stream
  • If upgrade is not immediately possible, remove the camel-smooks data format or component from any routes that process XML from untrusted origins, effectively disabling vulnerable external entity resolution
  • Configure a network layer firewall or monitoring rule to block or alert on outbound connections from the Camel process to internal network addresses after XML processing to prevent accidental or malicious internal network requests

Generated by OpenCVE AI on October 19, 2026 at 12:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 19 Oct 2026 11:00:00 +0000

Type Values Removed Values Added
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.
Title Apache Camel: Camel-Smooks XML External Entity Processing, external entities resolved by default
Weaknesses CWE-611
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-19T14:30:52.101Z

Reserved: 2026-09-10T11:43:50.047Z

Link: CVE-2026-88901

cve-icon Vulnrichment

Updated: 2026-10-19T14:30:44.317Z

cve-icon NVD

Status : Received

Published: 2026-10-19T11:17:25.340

Modified: 2026-10-19T15:17:09.097

Link: CVE-2026-88901

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T13:00:15Z

Weaknesses
  • CWE-611

    Improper Restriction of XML External Entity Reference