LiveActive security incident?Get immediate response
CVE Record

CVE-2026-41675: xmldom: XML node injection through unvalidated processing instruction 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 processing instruction data to be serialized into XML without validating or neutralizing the PI-closing sequence ?>. As a result, an attacker can terminate the processing instruction 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 vulnerability affects JavaScript projects using xmldom to build and serialize XML. If an attacker controls processing-instruction content, they may break out of that instruction and add XML nodes to the serialized output, potentially altering downstream data or decisions.

Executive priority

Treat as high priority for applications that process or generate XML from user, partner, or API input. Prioritize internet-facing and integration-heavy services because the main business risk is unauthorized alteration of XML data consumed by downstream systems.

Technical view

Affected xmldom versions do not validate or neutralize the processing-instruction closing sequence during serialization. This allows XML node injection into serialized output. The issue is tracked as CWE-91 and carries CVSS 4.0 score 8.7 with high integrity impact.

Likely exposure

Exposure is likely in Node.js or JavaScript applications that depend on xmldom or @xmldom/xmldom and serialize attacker-influenced XML processing instructions. Dependency-only presence is not enough; practical risk depends on reachable XML construction and serialization paths.

Exploitation context

The bundle says KEV is false and provides no cited evidence of active exploitation. The CVSS vector indicates network, low-complexity, unauthenticated exploitation without user interaction, but only where attacker-controlled processing-instruction data reaches XML serialization.

Researcher notes

Focus analysis on XMLSerializer behavior around processing instructions and integrity-sensitive consumers of serialized XML. The available sources identify patched @xmldom/xmldom releases and a fixing commit, but do not provide evidence of public exploitation or a separate fix for legacy unscoped xmldom.

Mitigation direction

  • Upgrade @xmldom/xmldom to 0.9.10 or 0.8.13, per vendor advisory.
  • Inventory legacy xmldom <=0.6.0 and plan migration to a patched maintained package.
  • Check Red Hat advisory status for any affected packaged products.
  • If upgrade is delayed, reduce reachable untrusted XML serialization paths.
  • Monitor vendor advisories for additional downstream product fixes.

Validation and detection

  • Search dependency lockfiles for xmldom and @xmldom/xmldom versions.
  • Confirm deployed artifacts use patched versions, not only source branches.
  • Review code paths creating processing instructions from external input.
  • Check whether serialized XML feeds authorization, configuration, signing, or integration workflows.
  • Verify SCA tools flag all direct and transitive affected dependencies.
Prepared
Confidence
high
Sources
9

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-41675 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
9Source 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-41675Attack 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 node injection via crafted processing instructions
other:Red Hat severity ratingcvssV3_1
  • 2026-05-07T05:01:58.399Z: Reported to Red Hat.
  • 2026-05-07T03:49:34.056Z: 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