CVE-2026-65899

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 81% 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 3.0.0 before 3.4.9 does not reset the retained Trusted Types policy when clearConfig() is called, so a DOMPurify instance reused across trust boundaries stays bound to a previously supplied TRUSTED_TYPES_POLICY. A later caller that requests RETURN_TRUSTED_TYPE output receives a TrustedHTML object created by the old (potentially unsafe) policy rather than a clean default, which can lead to script execution at a Trusted Types sink. Passing TRUSTED_TYPES_POLICY: null on the later call also does not clear the retained policy.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
43(Track)
EG Risk 43/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 28, 2026

Advisory Details (3)

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

DOMPurify before 3.4.9 Trusted Types Policy State Contamination | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dompurify-before-trusted-types-policy-state-contamination
github_commit

commit 825e617753ac (cure53/DOMPurify)

Fix landed in cure53/DOMPurify commit 825e617753ac — awaiting tagged release

https://github.com/cure53/DOMPurify/commit/825e617753ac1169306a542d3174a77f717a0cf6
github Patch Available🟡 PoC Available

Trusted Types policy survives `clearConfig()` and can poison later `RETURN_TRUSTED_TYPE` output · Advisory · cure53/DOMPurify · GitHub

https://github.com/cure53/DOMPurify/security/advisories/GHSA-vxr8-fq34-vvx9

Vendor Advisories for CVE-2026-65899(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
redhatgrafana13-1-main-13.1.3-0.1.3.hum12026-08-22redhat
redhatgrafana12-4-main-12.4.8-0.1.2.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 (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.4.5+dfsg-1 (8 versions)3.4.12+dfsg-1—
npm(1)
PackageVulnerable rangeFixed inDependents
dompurify—3.4.9—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 58× 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 110 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-65899?
CVE-2026-65899 is a medium vulnerability published on July 23, 2026. DOMPurify 3.0.0 before 3.4.9 does not reset the retained Trusted Types policy when clearConfig() is called, so a DOMPurify instance reused across trust boundaries stays bound to a previously supplied TRUSTEDTYPESPOLICY. A later caller that requests RETURNTRUSTEDTYPE output receives a TrustedHTML…
When was CVE-2026-65899 disclosed?
CVE-2026-65899 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-65899 actively exploited?
CVE-2026-65899 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 80.9% of all scored CVEs.
What is the CVSS score of CVE-2026-65899?
CVE-2026-65899 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-65899?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65899, 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-65899

Explore →

Is Your Infrastructure Affected by CVE-2026-65899?

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

Start Free Scan →Browse All CVEs