Is CVE-2026-41675 exploited in the wild?

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

How severe is CVE-2026-41675?

High severity, with a CVSS score of 7.5, published 7 May 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-41675?

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

How is CVE-2026-41675 attacked?

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

Am I affected by CVE-2026-41675?

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-41675: xmldom XML injection in XMLSerializer processing instructions

CVE-2026-41675 · Severity: high · CVSS 7.5 · Published 2026-05-07

xmldom is a JavaScript library used to parse and create XML documents. A security flaw allows attackers to inject malicious XML content into documents generated by the library. This could lead to data corruption or the bypass of security controls that rely on the integrity of the generated XML.

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

Quick answers

Is CVE-2026-41675 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41675 being exploited in the wild.
How severe is CVE-2026-41675?: High severity, with a CVSS score of 7.5, published 7 May 2026.
Which products and versions are affected?: @xmldom/xmldom (npm) SEMVER:introduced=0,fixed=0.8.13; xmldom (npm) SEMVER:introduced=0,last_affected=0.6.0.
Is there a fix for CVE-2026-41675?: Yes. @xmldom/xmldom (npm): upgrade to 0.8.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41675 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-41675?: 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.13 or later
```
npm install @xmldom/xmldom@0.8.13
```

Technical details

The vulnerability is classified as XML Injection (CWE-91) within the XMLSerializer component of xmldom. The root cause is the failure to validate attacker-controlled processing instruction (PI) data for the PI-closing sequence '?>' during serialization. An attacker can provide crafted input that terminates a processing instruction early, allowing the injection of arbitrary XML nodes into the serialized output. This can be exploited remotely if the application serializes user-provided data into XML. The issue is addressed in versions 0.9.10 and 0.8.13 by introducing a 'requireWellFormed' option that throws an error if injection-prone content is detected.

Affected products

xmldom xmldom <= 0.6.0
xmldom @xmldom/xmldom >= 0.9.0, < 0.9.10
xmldom @xmldom/xmldom < 0.8.13

Identifiers

CVE-2026-41675
GHSA-x6wf-f3px-wcqx

Timeline

2026-04-18: patched: Fixes released in versions 0.8.13 and 0.9.10
2026-05-07: disclosed: Public advisory published

References

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