Skip to content
Fencer Intel
medium 5.3

CVE-2026-71436 json

Mermaid XY Charts are vulnerable to an infinite loop DoS

published 3mo ago modified 18d ago also EUVD-2026-54241 , GHSA-2v8p-3f2j-5mp7

cvss
5.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

Mermaid is a JavaScript tool that uses Markdown-inspired text to create and modify diagrams and charts. From version 10.6.0 until 10.9.8 and 11.16.1, Mermaid XY Charts are vulnerable to an infinite loop denial of service in the setXAxisRangeData function when configuring an X-Axis with invalid parameters. Because each loop iteration appends an element to an array, this generally causes a RangeError to appear after a few seconds, but it may instead cause the page or JavaScript process to crash from memory exhaustion, depending on the environment. This issue is fixed in versions 10.9.8 and 11.16.1.

Patch / fix

  • npm mermaid 10.9.8, 11.16.1
  • mermaid_project mermaid 10.9.8, 11.16.1

Is CVE-2026-71436 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-71436 updated cvss 7.5

mermaid: Mermaid XY Charts: Denial of Service via invalid X-Axis parameters

  • Red Hat OpenShift Dev Spaces 3.30 devspaces/code-rhel9 1789145741
    fixed: vendor fix RHSA-2026:68754
  • Red Hat Build of Podman Desktop rh-podman-desktop.git 1.1.0 Red Hat OpenShift AI (RHOAI) rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9 Red Hat OpenShift Dev Spaces 3.30 devspaces/server-rhel9 1789163798, devspaces/openvsx-rhel9 1789144269, devspaces/traefik-rhel9 1788882066, devspaces/udi-base-rhel9 1788883444, devspaces/code-sshd-rhel9 1789144422, devspaces/dashboard-rhel9 1789162884, +8 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 4.0 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L
CNA 4.0 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
npm mermaid
>=10.6.0, <10.9.8
>=11.0.0-alpha.1, <11.16.1
10.9.8
11.16.1

Affected products

  • mermaid-js mermaid

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition
  • CWE-1325 Improperly Controlled Sequential Memory Allocation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of mermaid-js/mermaid published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.