How severe is GHSA-2v8p-3f2j-5mp7?

No CVSS score has been assigned to GHSA-2v8p-3f2j-5mp7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2v8p-3f2j-5mp7?

GHSA-2v8p-3f2j-5mp7 affects the following packages: mermaid (npm), mermaid (npm). Ecosystems affected: npm.

How do I fix GHSA-2v8p-3f2j-5mp7?

Update mermaid to 10.9.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2v8p-3f2j-5mp7 is resolved across your whole dependency graph.

How do I detect GHSA-2v8p-3f2j-5mp7 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mermaid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2v8p-3f2j-5mp7 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-2v8p-3f2j-5mp7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2v8p-3f2j-5mp7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2v8p-3f2j-5mp7?

GHSA-2v8p-3f2j-5mp7 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2v8p-3f2j-5mp7?

GHSA-2v8p-3f2j-5mp7 is classified as CWE-835 (CWE-835), CWE-1325 (CWE-1325). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2v8p-3f2j-5mp7 published, and has it been updated?

GHSA-2v8p-3f2j-5mp7 was published on August 6, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Mermaid XY Charts are vulnerable to an infinite loop DoSGHSA-2v8p-3f2j-5mp7

Fix: mermaid-js/mermaid#8022

GHSA-2v8p-3f2j-5mp7 is a CWE-835 vulnerability in mermaid. A fix is available for mermaid — see the affected versions and patch details below.

Also known asCVE-2026-71436

Published

Aug 6, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2v8p-3f2j-5mp7.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

mermaidnpm

26.0Mdownloads / week

Description

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.

Proof-of-concept

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

Patches

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

Workarounds

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

References

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mermaid`	≥ 10.6.0&&< 10.9.8	10.9.8`npm install mermaid@10.9.8`
📦npm	`mermaid`	≥ 11.0.0-alpha.1&&< 11.16.1	11.16.1`npm install mermaid@11.16.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mermaid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mermaid to 10.9.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2v8p-3f2j-5mp7 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat ships Mermaid (a JavaScript diagramming library) embedded in code-server based developer workbench images: OpenShift AI's odh-workbench-codeserver-datascience-cpu-py312 workbench image and OpenShift Dev Spaces' code-rhel9 image. The bundled version falls within the vulnerable range (>=10.6.0,<10.9.8 or below…

Workaround published by Red Hat

Avoid rendering or previewing untrusted Mermaid diagram content containing XY chart definitions with attacker-controlled X-Axis parameters in the affected workbench images until the pinned mermaid dependency is upgraded to 10.9.8+/11.16.1+.

Source: Red Hat security advisory for GHSA-2v8p-3f2j-5mp7 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenShift Dev Spaces 3.30	`devspaces/code-rhel9:1789145741`	RHSA-2026:68754

Frequently Asked Questions

### 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. #### Proof-of-concept ```txt xychart x-axis 1 --> 1 line [1, 2] ``` ### Patches This has been patched in https://github.com/mermaid-js/mermaid/commit/630aa7e5dd417e1f56bff2a1ce8df2