CVE-2026-88901

Description

A flaw was found in the Apache Camel Smooks component (camel-smooks). This vulnerability allows an unauthenticated remote attacker to cause information disclosure by submitting a crafted XML message containing external entity references. Because the component processes incoming XML data without restricting external entity resolution by default, an attacker can read arbitrary local files accessible to the host process or issue unauthorized requests to internal network services.

Statement

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.

Mitigation

--- 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)

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score8.2N/A8.2
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactNoneN/ANone
Availability ImpactLowN/ALow

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Application Data; Read Files or Directories

If the attacker is able to include a crafted DTD and a default entity resolver is enabled, the attacker may be able to access arbitrary files on the system. By submitting an XML file that defines an external entity with a file:// URI, an attacker can cause the processing application to read the contents of a local file. For example, a URI such as "file:///c:/winnt/win.ini" designates (in Windows) the file C:\Winnt\win.ini, or file:///etc/passwd designates the password file in Unix-based systems. Once the content of the URI is read, it is fed back into the application that is processing the XML. This application may echo back the data (e.g., in an error message), thereby exposing the file contents.

Integrity

Technical Impact: Bypass Protection Mechanism

An attacker may supply a crafted DTD using URIs with schemes such as http://, forcing the application to make outgoing HTTP requests to servers that the attacker cannot reach directly, which can be used to bypass firewall restrictions; hide the source of attacks such as port scanning; or otherwise leverage the server's trust relationship with other entities.

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)

The product could consume excessive CPU cycles or memory using a URI that points to a large file, or a device that always returns data such as /dev/random. Alternately, the URI could reference a file that contains many nested or recursive entity references to further slow down parsing.

Frequently Asked Questions

Want to get errata notifications? Sign up here.