VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

node-mermaid: vulnerability history, versions and safety

node-mermaid is a package in the Debian ecosystem. Vulert records 21 vulnerabilities for it across 15 releases, from Jun 2021 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
21 vulnerabilities recorded U21
i
15 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
9 in the last 12 months

Most recent disclosure 06 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all node-mermaid vulnerabilities

Vulert verdict on node-mermaid i

Updated on 23 Oct 2026

Careful: 15 of the 21 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 21 vulnerabilities on record across 5 years, 9 in the last year.

What to do: Plan around the 15 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 21 over 5 years · 9 in the last year i
  • Latest disclosure 06 Aug 2026 i
  • Highest CVSS 6.1 i
  • With no published fix 15 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for node-mermaid, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 15 of 15 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 4
  • 2022 4
  • 2023 2
  • 2025 2
  • 2026 9

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 9 of the 21 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for node-mermaid

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Cross-site Scripting Vulnerability in @braintree/sanitize-url Package 6.1 medium 8.7.0+ds+~cs27.17.17-3+deb11u1 16 Mar 2022
XSS Vulnerability in Mermaid Package: node-mermaid Affected by Antiscript Feature 6.1 medium 8.7.0+ds+~cs27.17.17-3 27 Jun 2021
CSS Injection Vulnerability in Mermaid Package: Information Disclosure Risk 6.1 medium No fix published 28 Jun 2022
XSS Vulnerability in sanitize-url Affects node-mermaid Package 6.1 medium No fix published 24 Feb 2023
JavaScript Code Execution Vulnerability in Mermaid Package 5.4 medium 8.7.0+ds+~cs27.17.17-3+deb11u2 30 Dec 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About node-mermaid

Is node-mermaid safe to use?

Vulert records 21 vulnerabilities for node-mermaid in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 21 not yet rated. 15 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does node-mermaid have?

21 vulnerabilities are recorded for node-mermaid in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 21 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new node-mermaid vulnerabilities disclosed?

9 vulnerabilities were recorded for node-mermaid in the last 12 months, and the oldest entry in this database dates to 27 Jun 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of node-mermaid are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor node-mermaid for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the node-mermaid version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.