DOMPurify before 3.4.0 contains a logic error in the ADD_TAGS function where short-circuit evaluation allows forbidden tags to bypass FORBID_TAGS restrictions. Attackers can craft input containing tags listed in FORBID_TAGS that are also added via ADD_TAGS function, causing them to be retained in sanitized output.
CVE-2026-65903
This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. 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(medium)
- EG Risk
- 28(Track)EG Risk 28/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%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 23, 2026DOMPurify before 3.4.0 ADD_TAGS Function Bypasses FORBID_TAGS | Advisories | VulnCheck
https://www.vulncheck.com/advisories/dompurify-before-add-tags-function-bypasses-forbid-tagsADD_TAGS function form bypasses FORBID_TAGS due to short-circuit evaluation · Advisory · cure53/DOMPurify · GitHub
https://github.com/cure53/DOMPurify/security/advisories/GHSA-39q2-94rc-95cpVendor Advisories for CVE-2026-65903(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 11× in last 7d / 11× 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-27 14:14 UTCEPSS rescore
- 2026-07-27 02:34 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:07 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 13:25 UTCEG score recompute
- 2026-07-23 13:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-697
- CVE-2023-32571EG 9.8EPSS p98CRITICAL
- CVE-2022-47034EG 9.8CRITICAL
- CVE-2014-125057NVD 3.1EG 9.8CRITICAL
- CVE-2021-27786NVD 4.6EG 9.8CRITICAL
- CVE-2021-44971EG 9.8CRITICAL
- CVE-2021-3833EG 9.8CRITICAL
- CVE-2021-35973EG 9.8CRITICAL
- CVE-2020-23361EG 9.8CRITICAL
- CVE-2020-23360EG 9.8CRITICAL
- CVE-2020-23359EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-65903?
When was CVE-2026-65903 disclosed?
Is CVE-2026-65903 actively exploited?
What is the CVSS score of CVE-2026-65903?
How do I remediate CVE-2026-65903?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65903
Is Your Infrastructure Affected by CVE-2026-65903?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.