CVE-2026-65913

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.3%, top 75% 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 — 3 sources updated 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 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.

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
25%
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 Prototype Pollution via USE_PROFILES | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dompurify-before-prototype-pollution-via-use-profiles
github Patch Available🟡 PoC Available

DOMPurify USE_PROFILES prototype pollution allows event handlers · Advisory · cure53/DOMPurify · GitHub

https://github.com/cure53/DOMPurify/security/advisories/GHSA-cj63-jhhr-wcxv

Vendor Advisories for CVE-2026-65913(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 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-dompurify3.1.7+dfsg+~3.0.5-2 ... 3.4.5+dfsg-1 (11 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 14× in last 7d / 66× 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.

Showing the most recent 100 of 120 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 03:07 UTCEG score recompute
  3. 2026-09-18 03:07 UTCVendor advisory
  4. 2026-09-17 04:34 UTCEG score recompute
  5. 2026-09-17 04:34 UTCVendor advisory
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 06:48 UTCEG score recompute
  8. 2026-09-16 06:48 UTCVendor advisory
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-14 10:16 UTCEG score recompute
  11. 2026-09-14 10:16 UTCVendor advisory
  12. 2026-09-13 12:17 UTCEG score recompute
  13. 2026-09-13 12:17 UTCVendor advisory
  14. 2026-09-12 14:31 UTCVendor advisory
  15. 2026-09-11 16:45 UTCEG score recompute
  16. 2026-09-11 16:45 UTCVendor advisory
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-11 09:37 UTCEPSS rescore
  19. 2026-09-10 15:11 UTCEG score recompute
  20. 2026-09-10 15:11 UTCVendor advisory
  21. 2026-09-09 08:57 UTCEG score recompute
  22. 2026-09-09 08:57 UTCVendor advisory
  23. 2026-09-08 22:01 UTCEPSS rescore
  24. 2026-09-07 21:31 UTCEG score recompute
  25. 2026-09-07 21:31 UTCVendor advisory
Show 75 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 17:26 UTCEG score recompute
  3. 2026-09-06 17:26 UTCVendor advisory
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-05 19:28 UTCEG score recompute
  6. 2026-09-05 19:28 UTCVendor advisory
  7. 2026-09-05 15:31 UTCEPSS rescore
  8. 2026-09-04 13:16 UTCEG score recompute
  9. 2026-09-04 13:16 UTCVendor advisory
  10. 2026-09-04 05:07 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 23:22 UTCEG score recompute
  13. 2026-09-01 23:22 UTCVendor advisory
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-30 22:20 UTCEG score recompute
  17. 2026-08-30 22:20 UTCVendor advisory
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-30 00:34 UTCEG score recompute
  21. 2026-08-30 00:34 UTCVendor advisory
  22. 2026-08-28 21:42 UTCEPSS rescore
  23. 2026-08-27 21:08 UTCEG score recompute
  24. 2026-08-27 21:08 UTCVendor advisory
  25. 2026-08-26 19:55 UTCEG score recompute
  26. 2026-08-26 19:55 UTCVendor advisory
  27. 2026-08-26 14:47 UTCEPSS rescore
  28. 2026-08-25 19:27 UTCEG score recompute
  29. 2026-08-25 19:27 UTCVendor advisory
  30. 2026-08-25 13:49 UTCEPSS rescore
  31. 2026-08-24 21:41 UTCEG score recompute
  32. 2026-08-24 21:41 UTCVendor advisory
  33. 2026-08-23 23:44 UTCVendor advisory
  34. 2026-08-23 01:58 UTCEG score recompute
  35. 2026-08-23 01:58 UTCVendor advisory
  36. 2026-08-23 00:19 UTCEPSS rescore
  37. 2026-08-22 04:12 UTCEG score recompute
  38. 2026-08-22 04:12 UTCVendor advisory
  39. 2026-08-21 23:49 UTCEPSS rescore
  40. 2026-08-21 06:26 UTCEG score recompute
  41. 2026-08-20 22:56 UTCEPSS rescore
  42. 2026-08-20 08:40 UTCEG score recompute
  43. 2026-08-19 17:04 UTCEPSS rescore
  44. 2026-08-19 10:54 UTCEG score recompute
  45. 2026-08-18 13:48 UTCEPSS rescore
  46. 2026-08-17 15:06 UTCEG score recompute
  47. 2026-08-17 13:47 UTCEPSS rescore
  48. 2026-08-16 17:20 UTCEG score recompute
  49. 2026-08-16 14:56 UTCEPSS rescore
  50. 2026-08-15 19:34 UTCEG score recompute
  51. 2026-08-15 01:30 UTCEPSS rescore
  52. 2026-08-14 00:02 UTCEG score recompute
  53. 2026-08-13 22:00 UTCEPSS rescore
  54. 2026-08-13 02:16 UTCEG score recompute
  55. 2026-08-12 13:51 UTCEPSS rescore
  56. 2026-08-12 04:30 UTCEG score recompute
  57. 2026-08-11 06:34 UTCEG score recompute
  58. 2026-08-11 00:00 UTCEPSS rescore
  59. 2026-08-10 08:48 UTCEG score recompute
  60. 2026-08-09 13:47 UTCEPSS rescore
  61. 2026-08-09 11:02 UTCEG score recompute
  62. 2026-08-08 16:37 UTCEPSS rescore
  63. 2026-08-08 13:17 UTCEG score recompute
  64. 2026-08-06 17:44 UTCEG score recompute
  65. 2026-08-06 13:47 UTCEPSS rescore
  66. 2026-08-05 19:58 UTCEG score recompute
  67. 2026-08-05 19:17 UTCEPSS rescore
  68. 2026-08-05 19:17 UTCEPSS rescore
  69. 2026-08-04 22:13 UTCEG score recompute
  70. 2026-08-04 15:10 UTCEPSS rescore
  71. 2026-08-04 10:39 UTCEPSS rescore
  72. 2026-08-04 00:26 UTCEG score recompute
  73. 2026-08-03 10:36 UTCEPSS rescore
  74. 2026-08-02 04:52 UTCEG score recompute
  75. 2026-08-02 02:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-65913?
CVE-2026-65913 is a medium vulnerability published on July 23, 2026. 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…
When was CVE-2026-65913 disclosed?
CVE-2026-65913 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-65913 actively exploited?
CVE-2026-65913 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 75.1% of all scored CVEs.
What is the CVSS score of CVE-2026-65913?
CVE-2026-65913 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-65913?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65913, 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-65913

Explore →

Is Your Infrastructure Affected by CVE-2026-65913?

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

Start Free Scan →Browse All CVEs