Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-88789 – XXE Injection (Local File Read / SSRF) – Apache Camel Quarkus 3.2.0–3.33.2 and 3.34

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-88789 is an Improper Restriction of XML External Entity Reference (XXE) vulnerability in the XSLT support extension of Apache Camel Quarkus (camel-quarkus-support-xalan). An attacker who can supply the XML document being transformed can read local files or issue requests to internal network locations via external entity declarations. The flaw carries a CVSS v3.1 base score of 8.6 (High).

Technical details

  • Root cause: camel-quarkus-support-xalan supplies its own Xalan-backed TransformerFactory to the xslt component and registers it as the JAXP default.
  • Xalan-J 2.7.x predates JAXP 1.5 and does not honor javax.xml.XMLConstants.ACCESS_EXTERNAL_DTD or ACCESS_EXTERNAL_STYLESHEET, so the external-access restrictions Apache Camel normally applies to its TransformerFactory are not in effect.
  • Trigger conditions: on the xslt component path, the issue affects message bodies that reach the transformer already as a javax.xml.transform.Source. Bodies of other types (String, byte[], InputStream) are converted by Apache Camel to a SAXSource with external entities and external DTD loading disabled, and are not affected.
  • Because the vulnerable factory is also registered as the JAXP default, any other code in the application that obtains a TransformerFactory via TransformerFactory.newInstance() silently loses the same restrictions.
  • Attack vector: network — an attacker supplies a crafted XML document (containing an external entity declaration) that is processed by the affected transformer.
  • Impact: disclosure of local files and the ability to issue requests to internal network resources (SSRF-style access), with no impact on integrity or availability.

Affected software

  • Apache Camel Quarkus 3.2.0 through 3.33.2 (inclusive)
  • Apache Camel Quarkus 3.34.0 through 3.39.x (inclusive)
  • Affected when any of the following extensions are on the classpath: camel-quarkus-xslt, camel-quarkus-xslt-saxon, camel-quarkus-tika, camel-quarkus-xmlsecurity (the latter three are exposed only through the JAXP default factory, not direct XSLT transformation)

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Apache Camel Quarkus 3.33.3 (LTS branch) or 3.40.0 (current branch), which fix the issue.
  • If immediate upgrade is not possible:
    • Avoid passing untrusted javax.xml.transform.Source objects directly to xslt endpoints; instead supply message bodies as String, byte[], or InputStream so Apache Camel converts them to a SAXSource with external entity and external DTD loading disabled.
    • Where application code relies on JAXP’s default TransformerFactory.newInstance(), explicitly request the JDK implementation (com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl) rather than relying on the default lookup, to avoid picking up the vulnerable Xalan-backed factory.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge