CVE-2026-71438

LOWPre-NVD 2.42.4—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (26th 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
2.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 2.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Mermaid is a JavaScript tool that uses Markdown-inspired text to create and modify diagrams and charts. Prior to 10.9.8 and 11.16.1, Mermaid's configuration setters (mermaid.initialize, mermaidAPI.setConfig, and mermaidAPI.updateSiteConfig) merge caller-supplied configuration into Mermaid's internal config using the assignWithDepth deep-merge helper, which is vulnerable to prototype pollution. This is only exploitable if an application forwards untrusted data directly into one of these configuration entry points, which is outside their documented usage; diagram-supplied configuration (e.g. %%{init: {}}%% or YAML frontmatter) is not affected. This issue is fixed in versions 10.9.8 and 11.16.1.

CVSS v3
2.4
EG Score
2.4LOWmedium confidence
EG Risk
11
EG Risk 11/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
Severity24% × 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.4%
EPSS %ILE
26th
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

August 6, 2026

Last Modified

September 8, 2026

Vendor Advisories for CVE-2026-71438(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 rangeFix by version rangeDependents
node-mermaid8.11.0+ds+~cs29.13.22-1 ... 9.2.2+~2.0.0-2 (15 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-mermaid8.11.0+ds+~cs29.13.22-1 ... 9.2.2+~2.0.0-2 (16 versions)
  • every version on: no fix on record
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
mermaid—
  • 11.0.0-alpha.1 up to 11.16.1: fixed in 11.16.1
  • every version up to 10.9.8: fixed in 10.9.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 08:17 UTCEG score recompute
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-01 19:50 UTCEPSS rescore
  5. 2026-10-01 06:55 UTCEG score recompute
  6. 2026-09-30 15:03 UTCEPSS rescore
  7. 2026-09-28 13:52 UTCEPSS rescore
  8. 2026-09-28 05:36 UTCEG score recompute
  9. 2026-09-27 13:48 UTCEPSS rescore
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-25 04:21 UTCEG score recompute
  12. 2026-09-23 17:54 UTCEPSS rescore
  13. 2026-09-21 21:09 UTCEPSS rescore
  14. 2026-09-21 12:46 UTCEG score recompute
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-18 02:35 UTCEG score recompute
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-15 01:20 UTCEG score recompute
  22. 2026-09-12 15:02 UTCEPSS rescore
  23. 2026-09-12 00:05 UTCEG score recompute
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-10 09:35 UTCEPSS rescore
Show 38 more
  1. 2026-09-08 22:01 UTCEPSS rescore
  2. 2026-09-08 04:45 UTCEG score recompute
  3. 2026-09-06 13:48 UTCEPSS rescore
  4. 2026-09-05 03:29 UTCEG score recompute
  5. 2026-09-04 05:07 UTCEPSS rescore
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-01 18:09 UTCEG score recompute
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 10:36 UTCEG score recompute
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-26 14:47 UTCEPSS rescore
  15. 2026-08-26 00:30 UTCEG score recompute
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-22 22:57 UTCEG score recompute
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-20 22:56 UTCEPSS rescore
  20. 2026-08-19 21:42 UTCEG score recompute
  21. 2026-08-19 17:04 UTCEPSS rescore
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 20:27 UTCEG score recompute
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-16 02:15 UTCEPSS rescore
  27. 2026-08-15 01:31 UTCEPSS rescore
  28. 2026-08-13 19:11 UTCEG score recompute
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-11 00:00 UTCEPSS rescore
  31. 2026-08-10 17:56 UTCEG score recompute
  32. 2026-08-09 13:47 UTCEPSS rescore
  33. 2026-08-08 16:37 UTCEPSS rescore
  34. 2026-08-07 16:23 UTCEG score recompute
  35. 2026-08-07 16:03 UTCEG score recompute
  36. 2026-08-06 22:37 UTCEG score recompute▲ 2.40
  37. 2026-08-06 22:37 UTCNVD updateCVSS v3 → 2.4 · CVSS v4 → 2.4
  38. 2026-08-06 20:07 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-71438?
CVE-2026-71438 is a low vulnerability published on August 6, 2026. Mermaid is a JavaScript tool that uses Markdown-inspired text to create and modify diagrams and charts. Prior to 10.9.8 and 11.16.1, Mermaid's configuration setters (mermaid.initialize, mermaidAPI.setConfig, and mermaidAPI.updateSiteConfig) merge caller-supplied configuration into Mermaid's…
When was CVE-2026-71438 disclosed?
CVE-2026-71438 was first published on August 6, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71438 actively exploited?
CVE-2026-71438 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71438?
CVE-2026-71438 has a CVSS base score of 2.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71438?
A fix for CVE-2026-71438 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71438 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-71438

Explore →

Is Your Infrastructure Affected by CVE-2026-71438?

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