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.3% (20th percentile of EPSS-scored CVEs). 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
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.3%CVSS: 7.2Exploit: None knownExposed services: Not assessed

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.2HIGHmedium confidence
EG Risk
33
EG Risk 33/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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
githubMentions a patch (unverified)🟡 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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
node-dompurify2.4.1+dfsg+~2.4.0-1 ... 3.4.5+dfsg-1 (18 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-dompurify3.1.7+dfsg+~3.0.5-2 ... 3.4.5+dfsg-1 (12 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-dompurify3.1.7+dfsg+~3.0.5-2 ... 3.4.5+dfsg-1 (8 versions)
  • every version up to 3.4.12+dfsg-1: fixed in 3.4.12+dfsg-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
dompurify—
  • every version up to 3.4.11: fixed in 3.4.11
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 56× 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 163 total refreshes for this CVE.

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

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 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.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65898?
CVE-2026-65898 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-65898?
A fix for CVE-2026-65898 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65898 are linked in the Vendor Advisories panel on this page.

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.