GHSA-mrv2-3pqr-j5jr: dompurify (CVE-2026-116803)

Package	Ecosystem	Affected	Fixed in
dompurify	npm	<3.4.17	3.4.17

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Affected: the npm package dompurify before 3.4.17, with 3.4.17 as the fixed version. In IN_PLACE mode, a hook that removes a node other than the one it was called for (such as the current node's parent or an unvisited sibling) leaves that detached subtree's event handlers active, so an already-loading element like an img with onerror can still fire after sanitize() returns. An attacker who supplies markup to an application that uses such a hook could get DOM XSS; the source frames this as an application choice rather than a default-configuration flaw. Upgrade to dompurify 3.4.17 or later.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
5.1	Medium	4.0	CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N	CNA (VulnCheck)

CISA KEV Not listed.
EPSS 0.0016, the 5th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

26 Oct 2026, 23:05 UTC Confirmed by the CVE List
31 Oct 2026, 13:33 UTC First seen by agentprime
31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.