Is CVE-2026-34601 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34601 being exploited in the wild.

How severe is CVE-2026-34601?

High severity, with a CVSS score of 7.5, published 2 April 2026.

Which products and versions are affected?

@xmldom/xmldom (npm) SEMVER:introduced=0,fixed=0.8.12; xmldom (npm) SEMVER:introduced=0,last_affected=0.6.0.

Is there a fix for CVE-2026-34601?

Yes. @xmldom/xmldom (npm): upgrade to 0.8.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34601 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-34601?

Check whether you run @xmldom/xmldom (npm) or xmldom (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34601: xmldom XML injection via unsafe CDATA serialization

CVE-2026-34601 · Severity: high · CVSS 7.5 · Published 2026-04-02

xmldom is a JavaScript library used to process and create XML documents. A security flaw allows attackers to insert special characters that break out of protected text areas, effectively injecting new commands or data into the XML structure. This can lead to the manipulation of business logic in applications that rely on this library to handle data securely.

Technologies: @xmldom/xmldom (npm), xmldom (npm). Vendors: npm.

Quick answers

Is CVE-2026-34601 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34601 being exploited in the wild.
How severe is CVE-2026-34601?: High severity, with a CVSS score of 7.5, published 2 April 2026.
Which products and versions are affected?: @xmldom/xmldom (npm) SEMVER:introduced=0,fixed=0.8.12; xmldom (npm) SEMVER:introduced=0,last_affected=0.6.0.
Is there a fix for CVE-2026-34601?: Yes. @xmldom/xmldom (npm): upgrade to 0.8.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34601 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-34601?: Check whether you run @xmldom/xmldom (npm) or xmldom (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@xmldom/xmldom (npm): upgrade to 0.8.12 or later
```
npm install @xmldom/xmldom@0.8.12
```

Technical details

The vulnerability is classified as XML Injection (CWE-91) within the xmldom library's XMLSerializer and DOMParser components. The root cause is the failure to reject or safely split the CDATA terminator sequence ']]>' when it appears within a CDATASection node. An attacker can provide a string containing this sequence via methods like createCDATASection, appendData, or textContent. During serialization, the XMLSerializer emits the content verbatim, allowing the attacker to close the CDATA section prematurely and inject arbitrary XML tags. This can be exploited remotely if the application processes untrusted input through these DOM methods. The issue is patched in xmldom 0.6.0, @xmldom/xmldom 0.8.12, and @xmldom/xmldom 0.9.9.

Affected products

xmldom xmldom <= 0.6.0
xmldom @xmldom/xmldom < 0.8.12, >= 0.9.0 < 0.9.9

Identifiers

CVE-2026-34601
GHSA-wh4c-j3r5-mjhp

Timeline

2026-03-29: patched: Fixes committed and releases 0.8.12 and 0.9.9 published.
2026-03-29: advisory: GitHub Security Advisory GHSA-wh4c-j3r5-mjhp published.
2026-04-02: disclosed: CVE-2026-34601 published.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.