DOMPurify before 3.3.2 contains a prototype pollution vulnerability in USE_PROFILES mode that allows attackers to bypass attribute filtering by polluting Array.prototype properties. Attackers can set Array.prototype properties like onclick to true, causing DOMPurify to accept event handlers as allowlisted attributes and resulting in DOM-based XSS when sanitized markup is rendered.
CVE-2026-65913
This medium-severity CVE scores 6.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(low)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- —
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 23, 2026DOMPurify before 3.3.2 Prototype Pollution via USE_PROFILES | Advisories | VulnCheck
https://www.vulncheck.com/advisories/dompurify-before-prototype-pollution-via-use-profilesDOMPurify USE_PROFILES prototype pollution allows event handlers · Advisory · cure53/DOMPurify · GitHub
https://github.com/cure53/DOMPurify/security/advisories/GHSA-cj63-jhhr-wcxvVendor Advisories for CVE-2026-65913(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 13:25 UTCEG score recompute
- 2026-07-23 13:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-1321
Frequently asked(4)
What is CVE-2026-65913?
When was CVE-2026-65913 disclosed?
What is the CVSS score of CVE-2026-65913?
How do I remediate CVE-2026-65913?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65913
Is Your Infrastructure Affected by CVE-2026-65913?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.