VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

showdown: vulnerability history, versions and safety

showdown is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 62 releases, from Sep 2020 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M3 L1
i
3 with no fix published

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

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

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all showdown vulnerabilities

Vulert verdict on showdown 2.1.0 i

Updated on 23 Oct 2026

Careful: 2.1.0 has 3 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.1.0 — affected i
  • Vulnerabilities on record 4 over 5 years · 2 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 6.1 i
  • With no published fix 3 i
  • Depended on by 961 packages i
  • Stars 14,872 i
  • OpenSSF scorecard 6/10 i
  • Last release 54 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for showdown, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.1.0 21 Apr 2022 M3 MIT No Details →
2.0.4 21 Apr 2022 M3 MIT No Details →
2.0.3 08 Mar 2022 M3 MIT No Details →
2.0.2 03 Mar 2022 M3 MIT No Details →
2.0.1 01 Mar 2022 M3 MIT No Details →
2.0.0 16 Feb 2022 M3 MIT No Details →
2.0.0-alpha 04 Feb 2022 M3 MIT No Details →
1.9.1 02 Nov 2019 M3 BSD-3-Clause No Details →
1.9.0 10 Nov 2018 M3 L1 BSD-3-Clause No Details →
1.8.7 16 Oct 2018 M3 L1 BSD-3-Clause No Details →
1.8.6 22 Dec 2017 M3 L1 BSD-3-Clause No Details →
1.8.5 10 Dec 2017 M3 L1 BSD-3-Clause No Details →
1.8.4 05 Dec 2017 M3 L1 BSD-3-Clause No Details →
1.8.3 28 Nov 2017 M3 L1 BSD-3-Clause No Details →
1.8.2 11 Nov 2017 M3 L1 BSD-3-Clause No Details →
1.8.1 01 Nov 2017 M3 L1 BSD-3-Clause No Details →
1.8.0 24 Oct 2017 M3 L1 BSD-3-Clause No Details →
1.7.6 06 Oct 2017 M3 L1 BSD-3-Clause No Details →
1.7.5 02 Oct 2017 M3 L1 BSD-3-Clause No Details →
1.7.4 08 Sep 2017 M3 L1 BSD-3-Clause No Details →
1.7.3 23 Aug 2017 M3 L1 BSD-3-Clause No Details →
1.7.2 05 Aug 2017 M3 L1 BSD-3-Clause No Details →
1.7.1 02 Jun 2017 M3 L1 BSD-3-Clause No Details →
1.7.0 01 Jun 2017 M3 L1 BSD-3-Clause No Details →
1.6.4 06 Feb 2017 M3 L1 BSD-3-Clause No Details →
1.6.3 30 Jan 2017 M3 L1 BSD-3-Clause No Details →
1.6.2 29 Jan 2017 M3 L1 BSD-3-Clause No Details →
1.6.1 28 Jan 2017 M3 L1 BSD-3-Clause No Details →
1.6.0 09 Jan 2017 M3 L1 BSD-3-Clause No Details →
1.5.5 30 Dec 2016 M3 L1 BSD-3-Clause No Details →
1.5.4 23 Dec 2016 M3 L1 BSD-3-Clause No Details →
1.5.3 19 Dec 2016 M3 L1 BSD-3-Clause No Details →
1.5.2 17 Dec 2016 M3 L1 BSD-3-Clause No Details →
1.5.1 01 Dec 2016 M3 L1 BSD-3-Clause No Details →
1.5.0 11 Nov 2016 M3 L1 BSD-3-Clause No Details →
1.4.4 02 Nov 2016 M3 L1 BSD-3-Clause No Details →
1.4.3 19 Aug 2016 M3 L1 BSD-3-Clause No Details →
1.4.2 21 Jun 2016 M3 L1 BSD-3-Clause No Details →
1.4.1 17 May 2016 M3 L1 BSD-3-Clause No Details →
1.4.0 13 May 2016 M3 L1 BSD-3-Clause No Details →
1.3.0 19 Oct 2015 M3 L1 BSD-2-Clause No Details →
1.2.3 27 Aug 2015 M3 L1 BSD-2-Clause No Details →
1.2.2 03 Aug 2015 M3 L1 BSD-2-Clause No Details →
1.2.1 22 Jul 2015 M3 L1 BSD-2-Clause No Details →
1.2.0 13 Jul 2015 M3 L1 BSD-2-Clause No Details →
1.1.0 18 Jun 2015 M3 L1 BSD-2-Clause No Details →
1.0.2 28 May 2015 M3 L1 non-standard No Details →
1.0.1 27 May 2015 M3 L1 non-standard No Details →
1.0.0 27 May 2015 M3 L1 non-standard No Details →
0.5.4 27 May 2015 M3 L1 MIT No Details →
0.5.3 27 May 2015 M3 L1 MIT No Details →
0.5.2 27 May 2015 M3 L1 MIT No Details →
1.0.0-alpha.2 15 May 2015 M3 L1 non-standard No Details →
1.0.0-alpha1 14 May 2015 M3 L1 MIT No Details →
0.5.0 22 Apr 2015 M3 L1 MIT No Details →
0.4.0 01 Mar 2015 M3 L1 MIT No Details →
0.3.4 01 Mar 2015 M3 L1 MIT No Details →
0.3.1 02 Nov 2012 M3 L1 MIT No Details →
0.3.0 31 Oct 2012 M3 L1 MIT No Details →
0.2.0 15 Jun 2012 M3 L1 MIT No Details →
0.1.0 15 Jun 2012 M3 L1 MIT No Details →
0.0.1 12 Apr 2011 M3 L1 MIT No Details →

All 62 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2024 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for showdown

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
showdown allows stored cross-site scripting through table header ID injection 6.1 medium No fix published 07 Jul 2026
CVE-2026-59711: Showdown Package Cross-Site Scripting Vulnerability in Metadata Title Handling 6.1 medium No fix published 06 Jul 2026
CVE-2024-1899: Showdown Package Vulnerable to ReDoS in Link Parsing 5.3 medium No fix published 26 Feb 2024
Reverse Tabnabbing Vulnerability in showdown 3.1 low 1.9.1 03 Sep 2020

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 showdown

Is showdown safe to use?

Vulert records 4 vulnerabilities for showdown in npm: 0 critical, 0 high, 3 medium and 1 low. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is showdown's Vulert package health score?

Vulert scores showdown 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of showdown affected?

Yes. 2.1.0, the version you would install today, has 3 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of showdown should I use?

2.1.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does showdown have?

4 vulnerabilities are recorded for showdown in the npm ecosystem: 0 critical, 0 high, 3 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new showdown vulnerabilities disclosed?

2 vulnerabilities were recorded for showdown in the last 12 months, and the oldest entry in this database dates to 03 Sep 2020. 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 showdown 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 showdown for upcoming vulnerabilities?

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