Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

xmldom has XML node injection through unvalidated processing instruction serialization

CVE-2026-41675GHSA-x6wf-f3px-wcqx

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @xmldom/xmldom

    Affected
    < 0.8.13>= 0.9.0, < 0.9.10
    Fixed in
    0.8.13, 0.9.10

  • npm xmldom

    Affected
    <= 0.6.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · 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 · score source
EPSS
  • CVE-2026-41675: 0.47% estimated exploitation activity in the next 30 days; percentile 40.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. --- Details The issue is in the DOM construction and serialization flow for processing instruction nodes. When createProcessingInstruction(target, data) is called, the supplied data string is stored directly on the node without validation. Later, when the document is serialized, the serializer writes PI nodes by concatenating <?, the target, a space, node.data, and ? directly. That behavior is unsafe because processing instructions are a syntax-sensitive context. The closing delimiter ? terminates the PI. If attacker-controlled input contains ?, the serializer does not preserve it as literal PI content. Instead, it emits output where the remainder of the payload is treated as live XML markup.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-x6wf-f3px-wcqx

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-x6wf-f3px-wcqx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41675

Advisory: xmldom has XML node injection through unvalidated processing instruction serialization
IDs: CVE-2026-41675, GHSA-x6wf-f3px-wcqx
Record: https://patchnext.com/advisories/cve-2026-41675 (revision 3, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: @xmldom/xmldom 0.9.10, 0.8.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @xmldom/xmldom: affected < 0.8.13; >= 0.9.0, < 0.9.10; fixed in 0.8.13, 0.9.10
- npm xmldom: affected <= 0.6.0

## Suggested inspection (read-only)
- `npm ls @xmldom/xmldom --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls xmldom --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @xmldom/xmldom, xmldom.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x6wf-f3px-wcqx (OSV record GHSA-x6wf-f3px-wcqx lists affected ranges: npm @xmldom/xmldom >=0 =0.9.0 =0 <=0.6.0)
- Verified: https://github.com/advisories/GHSA-x6wf-f3px-wcqx (GitHub-reviewed advisory GHSA-x6wf-f3px-wcqx lists affected ranges: npm @xmldom/xmldom >=0 =0.9.0 =0 <=0.6.0)

Commands are suggestions: review each one before running it.

Loading voting…