What is CVE-2026-41150?

CVE-2026-41150 is a medium-severity security vulnerability in mermaid (npm), affecting versions >= 11.0.0-alpha.1, <= 11.14.0. It is fixed in 11.15.0, 10.9.6.

How severe is CVE-2026-41150?

CVE-2026-41150 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of mermaid are affected by CVE-2026-41150?

mermaid (npm) versions >= 11.0.0-alpha.1, <= 11.14.0 is affected.

Is there a fix for CVE-2026-41150?

Yes. CVE-2026-41150 is fixed in 11.15.0, 10.9.6. Upgrade to this version or later.

Is CVE-2026-41150 exploitable, and should I be worried?

Whether CVE-2026-41150 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.

What actually determines whether CVE-2026-41150 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.

How do I fix CVE-2026-41150?

Upgrade: mermaid to 11.15.0 or later, mermaid to 10.9.6 or later.

CVE-2026-41150 in mermaid | Intelligent Application Security

Q: How severe is CVE-2026-41150?

CVE-2026-41150 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of mermaid are affected by CVE-2026-41150?

mermaid (npm) versions >= 11.0.0-alpha.1, <= 11.14.0 is affected.

Q: Is there a fix for CVE-2026-41150?

Yes. CVE-2026-41150 is fixed in 11.15.0, 10.9.6. Upgrade to this version or later.

Q: Is CVE-2026-41150 exploitable, and should I be worried?

Whether CVE-2026-41150 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.

Q: What actually determines whether CVE-2026-41150 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.

Q: How do I fix CVE-2026-41150?

Upgrade: mermaid to 11.15.0 or later, mermaid to 10.9.6 or later.

Summary

Workarounds

There are no workarounds available without updating to a newer version of mermaid.

Impact

Mermaid v11.14.0 and earlier are vulnerable to a denial-of-service attack when rendering gantt charts, if they use the excludes attribute to exclude all dates.

Example:

gantt
  excludes monday,tuesday,wednesday,thursday,friday,saturday,sunday
  DoS :2025-01-01, 1d

mermaid.parse is unaffected, unless you then call the ganttDb.getTasks() (which is called when rendering a diagram).

CVE-2026-41150 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.15.0, 10.9.6); upgrading removes the vulnerable code path.

Affected versions

mermaid (>= 11.0.0-alpha.1, <= 11.14.0) mermaid (<= 10.9.5)

Security releases

mermaid → 11.15.0 (npm) mermaid → 10.9.6 (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.

See it in your environment

Remediation advice

This has been patched in:

Frequently Asked Questions

What is CVE-2026-41150? CVE-2026-41150 is a medium-severity security vulnerability in mermaid (npm), affecting versions >= 11.0.0-alpha.1, <= 11.14.0. It is fixed in 11.15.0, 10.9.6.
How severe is CVE-2026-41150? CVE-2026-41150 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of mermaid are affected by CVE-2026-41150? mermaid (npm) versions >= 11.0.0-alpha.1, <= 11.14.0 is affected.
Is there a fix for CVE-2026-41150? Yes. CVE-2026-41150 is fixed in 11.15.0, 10.9.6. Upgrade to this version or later.
Is CVE-2026-41150 exploitable, and should I be worried? Whether CVE-2026-41150 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
What actually determines whether CVE-2026-41150 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.
How do I fix CVE-2026-41150?
- Upgrade mermaid to 11.15.0 or later
- Upgrade mermaid to 10.9.6 or later

Other vulnerabilities in mermaid

CVE-2026-41159 CVE-2026-41149 CVE-2026-41148 CVE-2025-54881 CVE-2025-54880