Security readout for executives and security teams
Plain-English summary
Applications using affected xmldom versions may let untrusted data escape an XML processing instruction and add unauthorized XML elements. This can corrupt security-sensitive documents or alter how downstream systems interpret them. Risk depends on whether attacker-controlled processing-instruction data is serialized and then trusted.
Executive priority
Prioritize remediation for internet-facing services and workflows producing trusted XML, signed documents, policy files, or integration messages. Patch promptly where untrusted input reaches serialization. Inventory-only systems or applications lacking this data path can be handled through normal dependency maintenance after validation.
Technical view
XMLSerializer fails to validate the processing-instruction closing sequence in affected releases. Crafted processing-instruction data can terminate that instruction early and inject additional XML nodes. The CVSS 4.0 score is 8.7, driven primarily by remotely reachable, low-complexity integrity impact without required privileges or user interaction.
Likely exposure
Exposure is most likely in Node.js applications or libraries using affected direct or transitive xmldom dependencies to serialize attacker-influenced processing instructions. Systems that only parse XML, never create such instructions, or never trust serialized output may have lower practical exposure.
Exploitation context
The supplied CVSS vector describes network-accessible, low-complexity exploitation requiring no privileges or user interaction. Successful abuse still requires a data path from attacker-controlled processing-instruction content to XML serialization and consequential downstream processing. The bundle reports KEV as false and provides no evidence of active exploitation.
Researcher notes
CWE-91 applies because improper neutralization permits XML injection during serialization. The stated impact is integrity-focused; the supplied CVSS vector claims no direct confidentiality or availability impact. Evidence does not establish exploit prevalence, affected downstream protocols, or a patched release for the legacy unscoped package.
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.
- Migrate legacy xmldom 0.6.0 or earlier to a supported, fixed scoped release.
- Temporarily prevent untrusted data from populating processing instructions until dependencies are updated.
- Review vendor and distribution advisories for packaged or transitive copies.
Validation and detection
- Inventory direct and transitive xmldom versions using lockfiles, manifests, and software bills of materials.
- Trace whether attacker-controlled data can reach processing-instruction creation and XML serialization.
- Test malformed processing-instruction closing data and confirm serialization cannot produce unauthorized sibling nodes.
- Verify deployed artifacts contain fixed versions, not only updated development manifests.
- Run regression tests for XML generation and downstream document validation after upgrading.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-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- 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
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
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——GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6redhat-SADPVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: 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
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-05-07T05:01:58.399Z: Reported to Red Hat.
- 2026-05-07T03:49:34.056Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/xmldom/xmldom/security/advisories/GHSA-x6wf-f3px-wcqxCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/xmldom/xmldom/commit/7207a4b0e0bcc228868075ed991665ef9f73b1c2CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/xmldom/xmldom/releases/tag/0.8.13CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/xmldom/xmldom/releases/tag/0.9.10CVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-41675CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2467629CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-41675.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:26234CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:60520CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.