CVE-2026-41674
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 …
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) `DOMParser` and `XMLSerializer` module. In @xmldom/xmldom prior to versions 0.9.10 and 0.8.13 and xmldom version 0.6.0 and prior, the package serializes DocumentType node fields (internalSubset, publicId, systemId) verbatim without any escaping or validation. When these fields are set programmatically to attacker-controlled strings, XMLSerializer.serializeToString can produce output where the DOCTYPE declaration is terminated early and arbitrary markup appears outside it. This issue has been patched in versions @xmldom/xmldom versions 0.9.10 and 0.8.13.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/xmldom/xmldom/security/advisories/GHSA-f6ww-3ggp-fr8h
- github.com/xmldom/xmldom/commit/372008f9ae0e20fd69f761c7b79e202598267314
- github.com/xmldom/xmldom/releases/tag/0.8.13
- github.com/xmldom/xmldom/releases/tag/0.9.10
- github.com/advisories/GHSA-f6ww-3ggp-fr8h
- nvd.nist.gov/vuln/detail/CVE-2026-41674
- access.redhat.com/errata/RHSA-2026:20034
- access.redhat.com/errata/RHSA-2026:21338
- nvd.nist.gov/vuln/detail/CVE-2026-41674
- cve.org/CVERecord?id=CVE-2026-41674
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.