Answer in brief
CVE-2026-65899 records a Medium severity (CVSS 5.1) vulnerability in DOMPurify before 3.4.9 Trusted Types Policy State Contamination. The current sources do not mark it as known exploited. The current feed maps cure53/DOMPurify (generic), dompurify (npm), dompurify (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps cure53/DOMPurify (generic), dompurify (npm), dompurify (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| cure53/DOMPurifygeneric | >=0 <3.4.9 | 3.4.9 |
| dompurifynpm | <3.4.9 | 3.4.9 |
| dompurifynpm | >=0 <3.4.9 | 3.4.9 |
Published upstream
Jul 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
DOMPurify 3.0.0 before 3.4.9 does not reset the retained Trusted Types policy when clearConfig() is called, so a DOMPurify instance reused across trust boundaries stays bound to a previously supplied TRUSTED_TYPES_POLICY. A later caller that requests RETURN_TRUSTED_TYPE output receives a TrustedHTML object created by the old (potentially unsafe) policy rather than a clean default, which can lead to script execution at a Trusted Types sink. Passing TRUSTED_TYPES_POLICY: null on the later call also does not clear the retained policy.
Quoted source text, attributed separately from HOL analysis.