CVE-2026-65912

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this week
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

A fix is available — apply it.

DOMPurify before 3.3.2 contains a URI validation bypass vulnerability when ADD_ATTR is provided as a predicate function via EXTRA_ELEMENT_HANDLING.attributeCheck. Attackers can supply a predicate that accepts specific attribute and tag combinations to bypass URI-safe validation, allowing unsafe protocols like javascript: to survive sanitization and execute as DOM-based XSS when the link is activated.

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 computed
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 28, 2026

Advisory Details (2)

Auto-updated Jul 23, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

DOMPurify before 3.3.2 URI Validation Bypass via ADD_ATTR | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dompurify-before-uri-validation-bypass-via-add-attr
github Patch Available🟡 PoC Available

DOMPurify ADD_ATTR predicate skips URI validation · Advisory · cure53/DOMPurify · GitHub

https://github.com/cure53/DOMPurify/security/advisories/GHSA-cjmm-f4jc-qw8r

Vendor Advisories for CVE-2026-65912(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgrafana12-4-main-12.4.8-0.1.2.hum12026-08-22redhat
redhatgrafana13-1-main-13.1.3-0.1.1.hum12026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-dompurify2.4.1+dfsg+~2.4.0-1 ... 3.4.5+dfsg-1 (15 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-dompurify3.1.7+dfsg+~3.0.5-2 ... 3.4.5+dfsg-1 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-dompurify3.1.7+dfsg+~3.0.5-2, 3.2.5+dfsg-13.3.2+dfsg-1—
npm(1)
PackageVulnerable rangeFixed inDependents
dompurify—3.3.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 54× 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.

  1. 2026-08-25 20:47 UTCEG score recompute
  2. 2026-08-25 20:47 UTCVendor advisory
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 18:32 UTCEG score recompute
  5. 2026-08-24 18:32 UTCVendor advisory
  6. 2026-08-23 16:32 UTCEG score recompute
  7. 2026-08-23 16:32 UTCVendor advisory
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 14:34 UTCEG score recompute
  10. 2026-08-22 14:34 UTCVendor advisory
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 12:35 UTCEG score recompute
  13. 2026-08-21 12:35 UTCVendor advisory
  14. 2026-08-20 22:56 UTCEPSS rescore
  15. 2026-08-20 10:34 UTCEG score recompute
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-19 08:35 UTCEG score recompute
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-18 06:36 UTCEG score recompute
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 04:37 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 02:37 UTCEG score recompute
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-13 22:40 UTCEG score recompute
Show 39 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-12 20:41 UTCEG score recompute
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-11 18:42 UTCEG score recompute
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-09 14:22 UTCEG score recompute
  7. 2026-08-09 13:47 UTCEPSS rescore
  8. 2026-08-08 16:37 UTCEPSS rescore
  9. 2026-08-08 12:24 UTCEG score recompute
  10. 2026-08-07 10:25 UTCEG score recompute
  11. 2026-08-06 13:47 UTCEPSS rescore
  12. 2026-08-06 08:26 UTCEG score recompute
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-05 06:27 UTCEG score recompute
  16. 2026-08-04 15:10 UTCEPSS rescore
  17. 2026-08-04 10:39 UTCEPSS rescore
  18. 2026-08-04 04:28 UTCEG score recompute
  19. 2026-08-03 10:36 UTCEPSS rescore
  20. 2026-08-03 02:29 UTCEG score recompute
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-02 00:30 UTCEG score recompute
  23. 2026-08-01 04:16 UTCEPSS rescore
  24. 2026-07-30 20:32 UTCEG score recompute
  25. 2026-07-30 01:30 UTCEPSS rescore
  26. 2026-07-28 15:59 UTCEG score recompute
  27. 2026-07-28 15:37 UTCEPSS rescore
  28. 2026-07-28 07:12 UTCEG score recompute
  29. 2026-07-27 14:14 UTCEPSS rescore
  30. 2026-07-27 05:07 UTCEG score recompute
  31. 2026-07-26 14:54 UTCEPSS rescore
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 03:07 UTCEG score recompute
  34. 2026-07-25 14:18 UTCEPSS rescore
  35. 2026-07-25 14:18 UTCEPSS rescore
  36. 2026-07-24 14:18 UTCEPSS rescore
  37. 2026-07-24 14:18 UTCEPSS rescore
  38. 2026-07-23 13:25 UTCEG score recompute
  39. 2026-07-23 13:24 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-65912?
CVE-2026-65912 is a medium vulnerability published on July 23, 2026. DOMPurify before 3.3.2 contains a URI validation bypass vulnerability when ADDATTR is provided as a predicate function via EXTRAELEMENT_HANDLING.attributeCheck. Attackers can supply a predicate that accepts specific attribute and tag combinations to bypass URI-safe validation, allowing unsafe…
When was CVE-2026-65912 disclosed?
CVE-2026-65912 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65912 actively exploited?
CVE-2026-65912 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.0% of all scored CVEs.
What is the CVSS score of CVE-2026-65912?
CVE-2026-65912 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-65912?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65912, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-65912

Explore →

Is Your Infrastructure Affected by CVE-2026-65912?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs