LiveActive security incident?Get immediate response
CVE Record

CVE-2026-41672: xmldom: XML node injection through unvalidated comment serialization

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 comment content to be serialized into XML without validating or neutralizing comment-breaking sequences. As a result, an attacker can terminate the comment 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.

HighCVSS 8.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Applications using affected xmldom packages may let untrusted text escape an XML comment and become new XML elements. This can corrupt or alter XML documents consumed by other systems, creating potentially serious integrity impacts without authentication or user interaction.

Executive priority

Prioritize remediation for internet-facing or cross-trust applications that serialize untrusted XML comments. Patch promptly where XML output influences sensitive workflows. Lower priority is reasonable only after confirming no attacker-controlled comment-to-serializer path exists.

Technical view

Affected serializers do not validate comment-breaking sequences in attacker-controlled comment content. During serialization, crafted content can close the comment and inject arbitrary XML nodes. The supplied CVSS 4.0 score is 8.7, reflecting network reachability, low complexity, and high integrity impact.

Likely exposure

Exposure requires an affected package version, attacker influence over XML comment content, and serialization of that content. Risk is greatest where generated XML drives security, configuration, identity, messaging, or business workflows. Dependency presence alone does not prove an exploitable data path.

Exploitation context

The supplied bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation. The vulnerability requires a reachable flow from untrusted comment data through XMLSerializer into output that another component processes or trusts.

Researcher notes

The core weakness maps to CWE-91: XML injection. Assessment should focus on data flow and downstream interpretation, not package detection alone. The supplied sources identify fixes for @xmldom/xmldom 0.8 and 0.9 branches; they do not name a fixed legacy xmldom release.

Mitigation direction

  • Upgrade @xmldom/xmldom 0.9.x to version 0.9.10 or later.
  • Upgrade @xmldom/xmldom 0.8.x to version 0.8.13 or later.
  • For legacy xmldom 0.6.0 or earlier, consult vendor guidance for a supported migration path.
  • Until upgraded, prevent untrusted data from becoming serialized XML comment content.
  • Review downstream systems that consume XML generated by affected applications.

Validation and detection

  • Inventory direct and transitive installations of xmldom and @xmldom/xmldom.
  • Confirm deployed versions, not only versions declared in package manifests.
  • Trace whether attacker-controlled input can populate comments passed to XML serialization.
  • Verify downstream consumers cannot receive unintended nodes from comment content.
  • After upgrading, run regression tests covering XML comment serialization and downstream parsing.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-91: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-41672 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N——GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-41672Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPxmldom: @xmldom/xmldom: xmldom: Arbitrary XML Node Injection
other:Red Hat severity ratingcvssV3_1
  • 2026-05-07T05:02:05.372Z: Reported to Red Hat.
  • 2026-05-07T03:36:16.914Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
xmldomxmldomxmldom <= 0.6.0, @xmldom/xmldom >= 0.9.0, < 0.9.10, @xmldom/xmldom < 0.8.13Listed
Weakness

CWE details

CWE-91

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-91 · source CWE mapping

XML Injection (aka Blind XPath Injection)

XML Injection (aka Blind XPath Injection) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs