Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.3

xmldom: XML fragment injection via invalid EntityReference.nodeName during requireWellFormed serialization

CVE-2026-83610GHSA-6gmq-8vp8-gcm6

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.7.0, <= 0.8.14>= 0.9.0, <= 0.9.11
    Fixed in
    0.9.12, 0.8.15

  • 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
6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-83610: 0.59% estimated exploitation activity in the next 30 days; percentile 48.25 (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 An EntityReference node can be created with an invalid, attacker-controlled name through Document.createEntityReference(name). When this node is serialized directly with: the invalid nodeName is emitted into the serialized XML fragment without validation or escaping. This can produce real XML markup in the serialized output. In the proof of concept below, the serialized fragment contains <injected/, and reparsing the fragment creates a real injected element. --- Details The issue appears to be in the serialization path for ENTITYREFERENCENODE. For several other node types, requireWellFormed: true performs specific validation checks before serialization. For example, comments, processing instructions, document types, and some character data cases are checked before being emitted. However, for ENTITYREFERENCENODE, the serializer appears to emit the node name directly in entity reference form: As a result, if nodeName contains characters that break out of the intended &name;…

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

    Published from ghsa record GHSA-6gmq-8vp8-gcm6

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-83610

Advisory: xmldom: XML fragment injection via invalid EntityReference.nodeName during requireWellFormed serialization
IDs: CVE-2026-83610, GHSA-6gmq-8vp8-gcm6
Record: https://patchnext.com/advisories/cve-2026-83610 (revision 1, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
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.12, 0.8.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @xmldom/xmldom: affected >= 0.7.0, <= 0.8.14; >= 0.9.0, <= 0.9.11; fixed in 0.9.12, 0.8.15
- 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://github.com/advisories/GHSA-6gmq-8vp8-gcm6 (GitHub-reviewed advisory GHSA-6gmq-8vp8-gcm6 lists affected ranges: npm @xmldom/xmldom >=0.7.0 =0.9.0 =0 <=0.6.0)

Commands are suggestions: review each one before running it.

Loading voting…