LiveActive security incident?Get immediate response
CVE Record

CVE-2026-41674: xmldom: XML injection through unvalidated DocumentType 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 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. 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

Affected xmldom applications can produce manipulated XML when untrusted data reaches document-type fields. An attacker may break out of the DOCTYPE declaration and insert arbitrary markup, potentially corrupting documents or changing how downstream systems interpret them. Exposure depends on application data flow; merely installing the package does not establish exploitability.

Executive priority

Prioritize remediation for internet-facing services and workflows where serialized XML affects transactions, configuration, signatures, or trusted integrations. Patch promptly after compatibility testing. Systems that never construct DocumentType nodes from untrusted data have lower immediate exposure, but vulnerable dependencies should still be tracked and updated.

Technical view

Affected versions serialize DocumentType internalSubset, publicId, and systemId values without validation or escaping. Attacker-controlled values can terminate the DOCTYPE early, placing arbitrary markup outside it. The supplied CVSS v4.0 score is 8.7, emphasizing high integrity impact. Fixed @xmldom/xmldom releases are 0.8.13 and 0.9.10.

Likely exposure

Highest risk exists where applications programmatically populate DocumentType fields from network-originated or otherwise untrusted input, then serialize XML for storage, transmission, signing, or downstream processing. Affected dependencies include xmldom 0.6.0 and earlier and the specified vulnerable @xmldom/xmldom release lines, including transitive installations.

Exploitation context

The supplied vector describes network-accessible, low-complexity exploitation without privileges or user interaction. However, exploitation requires an application-specific path from attacker-controlled input into DocumentType fields followed by serialization. The source bundle does not identify active exploitation, and the CVE is not listed as KEV.

Researcher notes

CWE-91 applies because unvalidated DocumentType fields cross a syntax boundary during serialization. Assessment should distinguish package presence from a reachable sink: field assignment, attacker influence, serialization, and security-relevant consumption must align. The provided evidence supports arbitrary markup injection and high integrity impact, but does not establish confidentiality loss, availability impact, or exploitation in the wild.

Mitigation direction

  • Upgrade @xmldom/xmldom 0.8.x to 0.8.13 or later.
  • Upgrade @xmldom/xmldom 0.9.x to 0.9.10 or later.
  • For legacy xmldom, consult vendor guidance and move to a maintained fixed release.
  • Until upgraded, prevent untrusted values from populating DocumentType fields.
  • Review downstream XML workflows that rely on serialized document integrity.

Validation and detection

  • Inventory direct and transitive installations of xmldom and @xmldom/xmldom.
  • Confirm deployed lockfiles and runtime artifacts contain a fixed scoped-package version.
  • Trace data flow into internalSubset, publicId, and systemId assignments.
  • Verify serialized XML cannot escape the intended DOCTYPE boundary.
  • Run regression tests covering rejected or safely handled untrusted DocumentType values.
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-41674 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-41674Attack 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: Arbitrary XML markup injection
other:Red Hat severity ratingcvssV3_1
  • 2026-05-07T05:01:25.803Z: Reported to Red Hat.
  • 2026-05-07T03:47:51.140Z: 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.