CVE-2026-88789
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Exploit Intelligence
Moderate risk: more likely to be exploited than 43% of all known CVEs.
References
Related Vulnerabilities
Other CWE-611 (XML External Entity (XXE)) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-34102 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2019-9670 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2022-28219 | Critical | 9.8 | 97% | - | - |
| CVE-2024-22024 | High | 8.3 | 95% | - | - |
| CVE-2024-38653 | High | 7.5 | 92% | - | - |
| CVE-2017-12629 | Critical | 9.8 | 92% | - | Fix |
Common questions
How do I fix CVE-2026-88789?
No published fix for CVE-2026-88789 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-88789 being actively exploited?
Not that we know of. CVE-2026-88789 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.52% is the estimated probability that it will be exploited in the next 30 days. That is higher than 43% of all scored CVEs.
How severe is CVE-2026-88789?
CVE-2026-88789 has a CVSS v3 base score of 8.6, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-88789
Markdown
[](https://tridentstack.com/cve/CVE-2026-88789)HTML
<a href="https://tridentstack.com/cve/CVE-2026-88789"><img src="https://tridentstack.com/cve/badge/CVE-2026-88789.svg" alt="CVE-2026-88789"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-01.