CVE-2026-71436

CVE-2026-71436 is a medium-severity security vulnerability in mermaid (npm), affecting versions >= 10.6.0, < 10.9.8. It is fixed in 10.9.8, 11.16.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Mermaid XY Charts are vulnerable to an infinite loop DoS

Proof-of-concept

xychart
  x-axis 1 --> 1
  line [1, 2]

Workarounds

There are no known workarounds. Please update to the latest version or apply the patch.

References

Impact

Mermaid XY Charts are vulnerable to an infinite loop DoS attack in the setXAxisRangeData(), when configuring an X-Axis with invalid parameters.

As each loop appends an element to an array, this would generally only cause an RangeError: Invalid array length to appear after a few seconds, but may cause the page/JavaScript process to crash due to memory exhaustion, depending on the environment.

Affected versions

mermaid (>= 10.6.0, < 10.9.8) mermaid (>= 11.0.0-alpha.1, < 11.16.1)

Security releases

mermaid → 10.9.8 (npm) mermaid → 11.16.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

This has been patched in https://github.com/mermaid-js/mermaid/commit/630aa7e5dd417e1f56bff2a1ce8df2c5ad08d289 and released in Mermaid v11.16.1.

A backport has been made for the v10 branch in ef60adc837d9d5107af21285f01e83dea309bd0a and was released in Mermaid v10.9.8

Frequently Asked Questions

  1. What is CVE-2026-71436? CVE-2026-71436 is a medium-severity security vulnerability in mermaid (npm), affecting versions >= 10.6.0, < 10.9.8. It is fixed in 10.9.8, 11.16.1.
  2. Which versions of mermaid are affected by CVE-2026-71436? mermaid (npm) versions >= 10.6.0, < 10.9.8 is affected.
  3. Is there a fix for CVE-2026-71436? Yes. CVE-2026-71436 is fixed in 10.9.8, 11.16.1. Upgrade to this version or later.
  4. Is CVE-2026-71436 exploitable, and should I be worried? Whether CVE-2026-71436 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2026-71436 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2026-71436?
    • Upgrade mermaid to 10.9.8 or later
    • Upgrade mermaid to 11.16.1 or later

Other vulnerabilities in mermaid

Stop the waste.
Protect your environment with Kodem.