Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.6amended

DOMPurify IN_PLACE: hook that removes a parent or sibling leaves the detached subtree's event handlers armed (incomplete fix for GHSA-p98j-92pf-mc4p)

CVE-2026-116803GHSA-mrv2-3pqr-j5jr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (dompurify 3.4.17), redeploy, then verify what is actually installed.

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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.6 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-116803: 0.16% estimated exploitation activity in the next 30 days; percentile 5.67 (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 3.4.16 fix for GHSA-p98j-92pf-mc4p only covers a hook that removes the node it was called for. If an `IN_PLACE` hook removes a different node, like the current node's parent or a sibling that has not been visited yet, that subtree is never walked or neutralized. Event handlers in it stay on the elements, and an ` ` that was already loading fires after `sanitize()` returns. The README says: "Nodes that a hook detaches from the tree ... are treated as removed. In IN_PLACE mode their subtree is neutralized inline, so an ` ` that was already loading when you built the live tree cannot fire after `sanitize()` returns." That does not hold when the detached node is not the hook's own node.

Tested versions - 3.4.16 (latest) and main at 18f8f0e - also 3.4.15, 3.4.12 and 2.5.8 jsdom for the matrix below, and Chromium (Playwright) for the event actually firing.

Details `src/purify.ts` line 2134 (`dist/purify.cjs.js` line 2009 in 3.4.16), `_handleHookDetachedNode()`:…

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

    Amended from osv record GHSA-mrv2-3pqr-j5jr

  2. Revision 5 · amended ·

    Amended from ghsa record GHSA-mrv2-3pqr-j5jr

  3. Revision 4 · amended ·

    Amended from ghsa record GHSA-mrv2-3pqr-j5jr

  4. Revision 3 · amended ·

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

  5. Revision 2 · amended ·

    Amended from osv record GHSA-mrv2-3pqr-j5jr

  6. Revision 1 · created ·

    Published from ghsa record GHSA-mrv2-3pqr-j5jr

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-116803

Advisory: DOMPurify IN_PLACE: hook that removes a parent or sibling leaves the detached subtree's event handlers armed (incomplete fix for GHSA-p98j-92pf-mc4p)
IDs: CVE-2026-116803, GHSA-mrv2-3pqr-j5jr
Record: https://patchnext.com/advisories/ghsa-mrv2-3pqr-j5jr (revision 6, source checked 28 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dompurify 3.4.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm dompurify: affected < 3.4.17; fixed in 3.4.17

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dompurify.
- 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://github.com/advisories/GHSA-mrv2-3pqr-j5jr (GitHub-reviewed advisory GHSA-mrv2-3pqr-j5jr lists affected ranges: npm dompurify >=0 <=3.4.16)
- Verified: https://osv.dev/vulnerability/GHSA-mrv2-3pqr-j5jr (OSV record GHSA-mrv2-3pqr-j5jr lists affected ranges: npm dompurify >=0 <3.4.17 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…