CVE-2026-65898

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% 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
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0

A fix is available — apply it.

DOMPurify before 3.4.11 fails to clone the ALLOWED_ATTR allowlist when setConfig() is used with an uponSanitizeAttribute hook, allowing the hook to permanently mutate the shared allowlist. Attackers can register a hook that conditionally allows dangerous attributes like onerror for trusted elements, then submit untrusted content that inherits the polluted allowlist and executes event handlers as stored XSS.

CVSS v3
7.2
EG Score
7.2(medium)
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 computed
Severity72% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
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.4.11 Permanent Attribute Allowlist Pollution via setConfig | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dompurify-before-permanent-attribute-allowlist-pollution-via-setconfig
github Patch Available🟡 PoC Available

Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch) · Advisory · cure53/DOMPurify · GitHub

https://github.com/cure53/DOMPurify/security/advisories/GHSA-cmwh-pvxp-8882

Vendor Advisories for CVE-2026-65898(2)

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.3.hum12026-08-22redhat

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.4.5+dfsg-1 (8 versions)3.4.12+dfsg-1—
npm(1)
PackageVulnerable rangeFixed inDependents
dompurify—3.4.11—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 17× in last 7d / 60× 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-26 05:40 UTCVendor advisory
  2. 2026-08-25 17:45 UTCEG score recompute
  3. 2026-08-25 17:45 UTCVendor advisory
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-25 05:46 UTCVendor advisory
  6. 2026-08-24 18:11 UTCEG score recompute
  7. 2026-08-24 18:11 UTCVendor advisory
  8. 2026-08-24 05:04 UTCVendor advisory
  9. 2026-08-23 17:28 UTCVendor advisory
  10. 2026-08-23 05:53 UTCEG score recompute
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 06:37 UTCEG score recompute
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 07:22 UTCEG score recompute
  15. 2026-08-20 22:56 UTCEPSS rescore
  16. 2026-08-19 20:34 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 19:00 UTCEG score recompute
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 14:30 UTCEG score recompute
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 15:18 UTCEG score recompute
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 03:42 UTCEG score recompute
  25. 2026-08-15 04:30 UTCEG score recompute
Show 46 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-12 18:26 UTCEG score recompute
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-11 19:14 UTCEG score recompute
  5. 2026-08-11 07:38 UTCEG score recompute
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-09 20:52 UTCEG score recompute
  8. 2026-08-09 13:47 UTCEPSS rescore
  9. 2026-08-08 21:41 UTCEG score recompute
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-07 22:29 UTCEG score recompute
  12. 2026-08-06 23:17 UTCEG score recompute
  13. 2026-08-06 13:47 UTCEPSS rescore
  14. 2026-08-06 00:05 UTCEG score recompute
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-05 00:33 UTCEG score recompute
  18. 2026-08-04 15:10 UTCEPSS rescore
  19. 2026-08-04 12:41 UTCEG score recompute
  20. 2026-08-04 10:39 UTCEPSS rescore
  21. 2026-08-03 11:48 UTCEG score recompute
  22. 2026-08-03 10:36 UTCEPSS rescore
  23. 2026-08-02 12:04 UTCEG score recompute
  24. 2026-08-02 02:27 UTCEPSS rescore
  25. 2026-08-01 12:51 UTCEG score recompute
  26. 2026-08-01 04:16 UTCEPSS rescore
  27. 2026-07-31 02:01 UTCEG score recompute
  28. 2026-07-30 16:28 UTCEPSS rescore
  29. 2026-07-30 14:24 UTCEG score recompute
  30. 2026-07-30 02:48 UTCEG score recompute
  31. 2026-07-30 01:30 UTCEPSS rescore
  32. 2026-07-28 15:59 UTCEG score recompute
  33. 2026-07-28 15:37 UTCEPSS rescore
  34. 2026-07-27 15:05 UTCEG score recompute
  35. 2026-07-27 14:14 UTCEPSS rescore
  36. 2026-07-27 02:23 UTCEG score recompute
  37. 2026-07-26 14:54 UTCEPSS rescore
  38. 2026-07-26 14:54 UTCEPSS rescore
  39. 2026-07-26 14:47 UTCEG score recompute
  40. 2026-07-26 03:09 UTCEG score recompute
  41. 2026-07-25 14:18 UTCEPSS rescore
  42. 2026-07-25 14:18 UTCEPSS rescore
  43. 2026-07-24 14:18 UTCEPSS rescore
  44. 2026-07-24 14:18 UTCEPSS rescore
  45. 2026-07-23 13:25 UTCEG score recompute
  46. 2026-07-23 13:24 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-65898?
CVE-2026-65898 is a high vulnerability published on July 23, 2026. DOMPurify before 3.4.11 fails to clone the ALLOWED_ATTR allowlist when setConfig() is used with an uponSanitizeAttribute hook, allowing the hook to permanently mutate the shared allowlist. Attackers can register a hook that conditionally allows dangerous attributes like onerror for trusted…
When was CVE-2026-65898 disclosed?
CVE-2026-65898 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-65898 actively exploited?
CVE-2026-65898 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 88.6% of all scored CVEs.
What is the CVSS score of CVE-2026-65898?
CVE-2026-65898 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-65898?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65898, 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-65898

Explore →

Is Your Infrastructure Affected by CVE-2026-65898?

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

Start Free Scan →Browse All CVEs