CVE-2026-41675
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 allows attacker-controlled processing instruction data to be serialized into XML without validating or neutralizing the PI-closing sequence ?>. As a result, an attacker can terminate the processing instruction early and inject arbitrary XML nodes into the serialized output. 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-x6wf-f3px-wcqx
- github.com/xmldom/xmldom/commit/7207a4b0e0bcc228868075ed991665ef9f73b1c2
- github.com/xmldom/xmldom/releases/tag/0.8.13
- github.com/xmldom/xmldom/releases/tag/0.9.10
- github.com/advisories/GHSA-x6wf-f3px-wcqx
- nvd.nist.gov/vuln/detail/CVE-2026-41675
- access.redhat.com/errata/RHSA-2026:26234
- access.redhat.com/security/cve/CVE-2026-41675
- nvd.nist.gov/vuln/detail/CVE-2026-41675
- cve.org/CVERecord?id=CVE-2026-41675
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.