Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
DOMPurify versions before 3.4.16 (npm dompurify) can return a force-removed rawtext root from the IN_PLACE path with its text content still carrying attacker markup, because the 3.4.9 attribute-only neutralization does not cover text. An attacker who can supply input sanitized in IN_PLACE mode can get script to run when the application serializes the returned node and re-parses it as HTML, although re-inserting the node with appendChild alone does not trigger it. The source describes the issue as reproduced on 3.4.15 and recommends upgrading to 3.4.16, which is listed as the fixed version.
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.0025, the 16th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 23 Sept 2026, 15:17 UTC Published by the maintainers as a GitHub repository advisory
- 31 Oct 2026, 13:33 UTC First seen by agentprime
- 31 Oct 2026, 13:33 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-6688-9rhm-gjv2
- OSV: GHSA-6688-9rhm-gjv2
- github.com/cure53/DOMPurify/security/advisories/GHSA-6688-9rhm-gjv2
- github.com/cure53/DOMPurify/pull/1636
- github.com/cure53/DOMPurify/commit/b9b9d80f7e401771c2ccaef5f45def7eec8f27d7
- github.com/cure53/DOMPurify
- github.com/cure53/DOMPurify/releases/tag/3.4.16