CVE-2026-47423

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% 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
Elevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. In 3.4.4, DOMPurify allowed selectedcontent by default, allowing browsers to re-clone an XSS payload after sanitization so that unsanitized markup inside is returned. This issue is fixed in version 3.4.5.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
53
EG Risk 53/100

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
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

Published

June 1, 2026

Last Modified

July 21, 2026

Advisory Details (3)

Auto-updated Jul 14, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

DOMPurify 3.4.5

Patch available: cure53/DOMPurify 3.4.5

https://github.com/cure53/DOMPurify/releases/tag/3.4.5
github_commit Patch Available

commit 011b0c78f2a0 (cure53/DOMPurify)

Patch available: cure53/DOMPurify 3.4.5 (contains commit 011b0c78f2a0)

https://github.com/cure53/DOMPurify/commit/011b0c78f2a0f57ee54f5fcccb697a46ca6e63ea
githubMentions a patch (unverified)🟡 PoC Available

DOMPurify XSS via `selectedcontent` re-clone · Advisory · cure53/DOMPurify · GitHub

https://github.com/cure53/DOMPurify/security/advisories/GHSA-87xg-pxx2-7hvx

Vendor Advisories for CVE-2026-47423(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatruff-main-0.15.11-1.hum12026-04-27redhat

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.2+dfsg-1 (7 versions)
  • every version up to 3.4.5+dfsg-1: fixed in 3.4.5+dfsg-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
dompurify3.4.4
  • 3.4.4 up to 3.4.5: fixed in 3.4.5
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 25× 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 136 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-47423?
CVE-2026-47423 is a high vulnerability published on June 1, 2026. DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. In 3.4.4, DOMPurify allowed selectedcontent by default, allowing browsers to re-clone an XSS payload after sanitization so that unsanitized markup inside <selectedcontent> is returned. This issue is fixed in version…
When was CVE-2026-47423 disclosed?
CVE-2026-47423 was first published on June 1, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47423 actively exploited?
CVE-2026-47423 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47423?
CVE-2026-47423 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47423?
A fix for CVE-2026-47423 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47423 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-47423

Explore →

Is Your Infrastructure Affected by CVE-2026-47423?

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