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

This flaw lets untrusted text placed inside XML comments escape the comment and add new XML nodes during serialization. The main business risk is integrity: downstream systems may process XML the application did not intend to create. It matters most where XML output drives access, configuration, business transactions, or security decisions.

Executive priority

Treat this as a high-priority dependency remediation for systems that generate XML from user-controlled input. Prioritize internet-facing services and workflows where XML integrity affects approvals, identity, configuration, billing, or partner integrations.

Technical view

Affected xmldom versions do not validate comment-breaking sequences before XMLSerializer output. An attacker controlling comment content can terminate the serialized comment early and inject arbitrary XML nodes. Sources identify CWE-91 and CVSS 4.0 score 8.7, with network attack vector, low complexity, no privileges, no user interaction, and high vulnerable-system integrity impact.

Likely exposure

Exposure is likely in Node.js applications using xmldom or @xmldom/xmldom to serialize XML containing attacker-controlled comment content. Risk is higher when serialized XML is trusted by other services, parsers, policy engines, import pipelines, or signing workflows.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Exploitation requires an application path where attacker-controlled content becomes an XML comment and the serialized output is later consumed in a security- or business-relevant context.

Researcher notes

The strongest evidence is the GitHub advisory and patch/release references. Impact is integrity-focused, not confidentiality or availability per the provided CVSS vector. No public-source evidence in the bundle establishes active exploitation. Product impact beyond xmldom package consumers should be verified through dependency inventory.

Mitigation direction

  • Upgrade @xmldom/xmldom to 0.9.10 or 0.8.13, as appropriate.
  • For legacy xmldom <=0.6.0, migrate to a patched supported package version.
  • Rebuild and redeploy applications after dependency updates.
  • Audit XML comment serialization paths that accept user-controlled data.
  • Check Red Hat RHSA-2026:26234 if using Red Hat-packaged components.

Validation and detection

  • Review lockfiles, SBOMs, and dependency reports for xmldom and @xmldom/xmldom versions.
  • Confirm deployed artifacts contain patched package versions, not only source branches.
  • Identify XMLSerializer usage where comment nodes include external or user-controlled content.
  • Review downstream consumers of generated XML for trust or authorization decisions.
  • Track vendor advisories for any product-specific backports or mitigations.
Prepared
Confidence
high
Sources
12

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
11Source 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