CVE-2026-41240

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% 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, nvd
Elevated
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: Elevated riskExposed: 0

A fix is available — apply it.

DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Versions prior to 3.4.0 have an inconsistency between FORBID_TAGS and FORBID_ATTR handling when function-based ADD_TAGS is used. Commit c361baa added an early exit for FORBID_ATTR at line 1214. The same fix was not applied to FORBID_TAGS. At line 1118-1123, when EXTRA_ELEMENT_HANDLING.tagCheck returns true, the short-circuit evaluation skips the FORBID_TAGS check entirely. This allows forbidden elements to survive sanitization with their attributes intact. Version 3.4.0 patches the issue.

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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

April 23, 2026

Last Modified

April 29, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

FORBID_TAGS bypassed by function-based ADD_TAGS predicate (asymmetry with FORBID_ATTR fix) · Advisory · cure53/DOMPurify · GitHub

https://github.com/cure53/DOMPurify/security/advisories/GHSA-h7mw-gpvr-xq4m
github_release Patch Available

DOMPurify 3.4.0

Patch available: cure53/DOMPurify 3.4.0

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

commit c361baa18dbd (cure53/DOMPurify)

Patch available: cure53/DOMPurify 3.3.3 (contains commit c361baa18dbd)

https://github.com/cure53/DOMPurify/commit/c361baa18dbdcb3344a41110f4c48ad85bf48f80

Patch Availability(15)

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.2.5+dfsg-1, 3.3.2+dfsg-1, 3.3.3+dfsg-1, 3.3.3+dfsg-23.4.1+dfsg-1
npm(1)
PackageVulnerable rangeFixed inDependents
dompurify3.4.0

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-41240?
CVE-2026-41240 is a medium vulnerability published on April 23, 2026. DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Versions prior to 3.4.0 have an inconsistency between FORBIDTAGS and FORBIDATTR handling when function-based ADDTAGS is used. Commit c361baa added an early exit for FORBIDATTR at line 1214. The same fix was not…
When was CVE-2026-41240 disclosed?
CVE-2026-41240 was first published in the National Vulnerability Database on April 23, 2026, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41240 actively exploited?
CVE-2026-41240 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 76.4% of all scored CVEs.
What is the CVSS score of CVE-2026-41240?
CVE-2026-41240 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-41240?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41240, 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-41240

Explore →

Is Your Infrastructure Affected by CVE-2026-41240?

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