CVE-2026-41148

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Mermaid is a JavaScript tool that uses Markdown-inspired text to create and modify diagrams and charts. Versions 10.9.5 and prior, in addition to 11.0.0-alpha.1 through 11.12.0 are vulnerable to CSS injection through improper sanitization. The state diagram (and any other diagram type that routes user-controlled style strings through the createCssStyles parser) captures classDef values using an unrestricted regex that matches everything up to a newline. That value then flows unsanitized through addStyleClass() into createCssStyles() and is assigned to style.innerHTML, so a closing brace (}) in the value terminates the generated CSS selector and turns everything after it into a new CSS rule on the page. This enables page defacement, user tracking via url() callbacks, and DOM attribute exfiltration. This issue has been fixed in versions 10.9.6 and 11.15.0. If developers are unable to immediately upgrade, they can work around this issue by setting "securityLevel": "sandbox", which prevents the issue by rendering the mermaid diagram in a sandboxed .

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

May 22, 2026

Last Modified

July 23, 2026

Advisory Details (6)

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

v10.9.6

Patch available: mermaid-js/mermaid v10.9.6

https://github.com/mermaid-js/mermaid/releases/tag/v10.9.6
github_commit Patch Available

commit e9b0f34d8d82 (mermaid-js/mermaid)

Patch available: mermaid-js/mermaid [email protected] (contains commit e9b0f34d8d82)

https://github.com/mermaid-js/mermaid/commit/e9b0f34d8d82a6260077764ee45e1d7d90957a0f
github_commit Patch Available

commit 8fead23c5916 (mermaid-js/mermaid)

Patch available: mermaid-js/mermaid v10.9.6 (contains commit 8fead23c5916)

https://github.com/mermaid-js/mermaid/commit/8fead23c59166b7bab6a39eac81acebee2859102
github Patch Available🟡 PoC Available

Improper sanitization of `classDefs` in diagrams leads to CSS injection · Advisory · mermaid-js/mermaid · GitHub

https://github.com/mermaid-js/mermaid/security/advisories/GHSA-xcj9-5m2h-648r

Vendor Advisories for CVE-2026-41148(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-mermaid8.11.0+ds+~cs29.13.22-1 ... 9.2.2+~2.0.0-2 (15 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-mermaid8.11.0+ds+~cs29.13.22-1 ... 9.2.2+~2.0.0-2 (16 versions)
npm(1)
PackageVulnerable rangeFixed inDependents
mermaid10.9.6

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-41148?
CVE-2026-41148 is a medium vulnerability published on May 22, 2026. Mermaid is a JavaScript tool that uses Markdown-inspired text to create and modify diagrams and charts. Versions 10.9.5 and prior, in addition to 11.0.0-alpha.1 through 11.12.0 are vulnerable to CSS injection through improper sanitization. The state diagram (and any other diagram type that routes…
When was CVE-2026-41148 disclosed?
CVE-2026-41148 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41148 actively exploited?
CVE-2026-41148 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 73.5% of all scored CVEs.
What is the CVSS score of CVE-2026-41148?
CVE-2026-41148 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-41148?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41148, 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-41148

Explore →

Is Your Infrastructure Affected by CVE-2026-41148?

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