Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting node-mermaid package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.35% (27th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN11-NODEMERMAID-18582776
  • published7 Aug 2026
  • disclosed6 Aug 2026

Introduced: 6 Aug 2026

CVE-2026-71438  (opens in a new tab)
CWE-1321  (opens in a new tab)

How to fix?

There is no fixed version for Debian:11 node-mermaid.

NVD Description

Note: Versions mentioned in the description apply only to the upstream node-mermaid package and not the node-mermaid package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

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.