Skip to main content
VulnerabilityPublished

CVE-2026-88789: Apache Camel Quarkus · XML External Entity (XXE)

Affects Apache Camel QuarkusSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 3.40.0 or 3.33.3 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.40.0, 3.33.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade Apache to 3.40.0 or 3.33.3.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache Camel QuarkusAffected
  • >=3.34.0 <3.40.0
Fixed in
  • 3.40.0
Apache Software FoundationApache Camel QuarkusAffected
  • >=3.2.0 <3.33.3
Fixed in
  • 3.33.3
MavenApache Software Foundation/org.apache.camel.quarkus:camel-quarkus-support-xalanpkg:maven/Apache Software Foundation/org.apache.camel.quarkus:camel-quarkus-support-xalanOther threatsAffected
  • >=3.2.0 <3.33.3
  • >=3.34.0 <3.40.0
Fixed in
  • 3.33.3
  • 3.40.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Camel Quarkus to version 3.33.3 or 3.40.0 or later, where this vulnerability is fixed. No other mitigation is indicated or required as the fix addresses the root cause by correcting the TransformerFactory behavior.

Description

Improper Restriction of XML External Entity Reference in the XSLT support extension (camel-quarkus-support-xalan) in Apache Camel Quarkus from 3.2.0 before 3.33.3 and from 3.34.0 before 3.40.0 on all platforms allows an attacker who supplies the XML document being transformed to read local files or issue requests to internal network locations via an external entity declaration in that document. The extension 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 honour javax.xml.XMLConstants.ACCESS_EXTERNAL_DTD or ACCESS_EXTERNAL_STYLESHEET, so the external access restrictions Apache Camel applies to the TransformerFactory it creates were not in effect. On the xslt component path this affects message bodies that reach the transformer already as a javax.xml.transform.Source; bodies of other types are converted to a SAXSource by Apache Camel with external entities and external DTD loading disabled, and are not affected. Because the factory is also the JAXP default, other code in the application obtaining one through TransformerFactory.newInstance() loses the same restrictions without error. Applications are affected if they use any of camel-quarkus-xslt, camel-quarkus-xslt-saxon, camel-quarkus-tika or camel-quarkus-xmlsecurity, each of which brings the XSLT support extension onto the classpath. For all but camel-quarkus-xslt, the exposure is limited to the JAXP default factory, since those extensions do not perform XSLT transformations themselves. Users are recommended to upgrade to version 3.33.3 or 3.40.0, which fixes this issue.

References

Community reviews

Loading reviews…