Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

xmldom has XML injection through unvalidated DocumentType serialization

CVE-2026-41674GHSA-f6ww-3ggp-fr8h

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @xmldom/xmldom

    Affected
    < 0.8.13>= 0.9.0, < 0.9.10
    Fixed in
    0.8.13, 0.9.10

  • npm xmldom

    Affected
    <= 0.6.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-41674: 0.56% estimated exploitation activity in the next 30 days; percentile 47.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. --- Details DOMImplementation.createDocumentType(qualifiedName, publicId, systemId, internalSubset) validates only qualifiedName against the XML QName production. The remaining three arguments are stored as-is with no validation. The XMLSerializer emits DocumentType nodes as: All fields are pushed into the output buffer verbatim — no escaping, no quoting added. internalSubset injection: The serializer wraps internalSubset with [ and ]. A value containing ] closes the internal subset and the DOCTYPE declaration at the injection point. Any content after ] in internalSubset appears outside the DOCTYPE in the serialized output as raw XML…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-f6ww-3ggp-fr8h

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-f6ww-3ggp-fr8h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41674

Advisory: xmldom has XML injection through unvalidated DocumentType serialization
IDs: CVE-2026-41674, GHSA-f6ww-3ggp-fr8h
Record: https://patchnext.com/advisories/cve-2026-41674 (revision 3, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: @xmldom/xmldom 0.9.10, 0.8.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @xmldom/xmldom: affected < 0.8.13; >= 0.9.0, < 0.9.10; fixed in 0.8.13, 0.9.10
- npm xmldom: affected <= 0.6.0

## Suggested inspection (read-only)
- `npm ls @xmldom/xmldom --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls xmldom --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @xmldom/xmldom, xmldom.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-f6ww-3ggp-fr8h (OSV record GHSA-f6ww-3ggp-fr8h lists affected ranges: npm @xmldom/xmldom >=0 =0.9.0 =0 <=0.6.0)
- Verified: https://github.com/advisories/GHSA-f6ww-3ggp-fr8h (GitHub-reviewed advisory GHSA-f6ww-3ggp-fr8h lists affected ranges: npm @xmldom/xmldom >=0 =0.9.0 =0 <=0.6.0)

Commands are suggestions: review each one before running it.

Loading voting…