# DOMPurify: IN_PLACE returns a force-removed rawtext root whose text carries attacker markup — pure HTML reparse executes Advisory record · `GHSA-6688-9rhm-gjv2` - **Identifiers:** `GHSA-6688-9rhm-gjv2` · `CVE-2026-109345` - **State:** Confirmed - **Severity:** CVSS 5.1 Medium - **Critical:** No - **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html) - **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md) - **Published:** 5 Oct 2026 - **Updated:** 13 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 5 Oct 2026, 23:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `dompurify` (npm): affected `<3.4.16`; fixed in `3.4.16` ## 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. 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 - 5.1 Medium, CVSS 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`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.0025, the 16th percentile, on 15 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](https://github.com/cure53/DOMPurify/security/advisories/GHSA-6688-9rhm-gjv2) - 31 Oct 2026, 13:33 UTC: First seen by agentprime - 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6688-9rhm-gjv2) ## Sources - [GitHub Advisory Database: GHSA-6688-9rhm-gjv2](https://github.com/advisories/GHSA-6688-9rhm-gjv2) - [OSV: GHSA-6688-9rhm-gjv2](https://osv.dev/vulnerability/GHSA-6688-9rhm-gjv2) - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .