VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

markdown-it: vulnerability history, versions and safety

markdown-it is a package in the npm ecosystem. Vulert records 9 vulnerabilities for it across 86 releases, from Jan 2022 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H3 M5 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
7 in the last 12 months

Most recent disclosure 20 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all markdown-it vulnerabilities

Vulert verdict on markdown-it 15.0.3 i

Updated on 23 Oct 2026

Good news: 15.0.3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 9.

Package health score 69/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 15.0.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 15.0.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 15.0.3 — unaffected i
  • Vulnerabilities on record 9 over 4 years · 7 in the last year i
  • Latest disclosure 20 Oct 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 719 packages i
  • Stars 21,979 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 markdown-it, 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
14.3.3 16 Oct 2026 none MIT — Details →
15.0.3 16 Oct 2026 none MIT — Details →
14.3.2 12 Sep 2026 H1 L1 MIT Yes Details →
15.0.2 11 Sep 2026 none MIT — Details →
15.0.1 27 Aug 2026 H1 MIT Yes Details →
14.3.1 27 Aug 2026 H1 L1 MIT Yes Details →
15.0.0 30 Jul 2026 M1 MIT Yes Details →
14.3.0 02 Jul 2026 H1 L1 MIT Yes Details →
14.2.0 23 May 2026 H1 L1 MIT Yes Details →
14.1.1 11 Feb 2026 H1 M2 L1 MIT Yes Details →
14.1.0 18 Mar 2024 H1 M3 L1 MIT Yes Details →
14.0.0 08 Dec 2023 M3 L1 MIT Yes Details →
13.0.2 26 Sep 2023 M3 L1 MIT Yes Details →
13.0.1 03 May 2022 M3 L1 MIT Yes Details →
13.0.0 22 Apr 2022 M3 L1 MIT Yes Details →
12.3.2 08 Jan 2022 M2 L1 MIT Yes Details →
12.3.1 07 Jan 2022 M3 L1 MIT Yes Details →
12.3.0 09 Dec 2021 M3 L1 MIT Yes Details →
12.2.0 02 Aug 2021 M3 L1 MIT Yes Details →
12.1.0 01 Jul 2021 M3 L1 MIT Yes Details →
12.0.6 16 Apr 2021 M3 L1 MIT Yes Details →
12.0.5 14 Apr 2021 M3 L1 MIT Yes Details →
12.0.4 20 Dec 2020 M3 L1 MIT Yes Details →
12.0.3 07 Dec 2020 M3 L1 MIT Yes Details →
12.0.2 23 Oct 2020 M3 L1 MIT Yes Details →
12.0.1 19 Oct 2020 M3 L1 MIT Yes Details →
12.0.0 14 Oct 2020 M3 L1 MIT Yes Details →
11.0.1 14 Sep 2020 M3 L1 MIT Yes Details →
11.0.0 19 May 2020 M3 L1 MIT Yes Details →
10.0.0 10 Sep 2019 M3 L1 MIT Yes Details →
9.1.0 11 Aug 2019 M3 L1 MIT Yes Details →
9.0.1 12 Jul 2019 M3 L1 MIT Yes Details →
9.0.0 09 Jul 2019 M3 L1 MIT Yes Details →
8.4.2 17 Jul 2018 M3 L1 MIT Yes Details →
8.4.1 15 Feb 2018 M3 L1 MIT Yes Details →
8.4.0 24 Aug 2017 M3 L1 MIT Yes Details →
8.3.2 03 Aug 2017 M3 L1 MIT Yes Details →
8.3.1 06 Mar 2017 M3 L1 MIT Yes Details →
8.3.0 16 Feb 2017 M3 L1 MIT Yes Details →
8.2.2 14 Dec 2016 M3 L1 MIT Yes Details →
8.2.1 01 Dec 2016 M3 L1 MIT Yes Details →
8.2.0 01 Dec 2016 M3 L1 MIT Yes Details →
8.1.0 03 Nov 2016 M3 L1 MIT Yes Details →
8.0.1 18 Oct 2016 M3 L1 MIT Yes Details →
8.0.0 16 Sep 2016 M3 L1 MIT Yes Details →
7.0.1 16 Aug 2016 M3 L1 MIT Yes Details →
7.0.0 22 Jun 2016 M3 L1 MIT Yes Details →
6.1.1 21 Jun 2016 M3 L1 MIT Yes Details →
6.1.0 19 Jun 2016 M3 L1 MIT Yes Details →
6.0.5 01 Jun 2016 M3 L1 MIT Yes Details →
6.0.4 30 May 2016 M3 L1 MIT Yes Details →
6.0.3 30 May 2016 M3 L1 MIT Yes Details →
6.0.2 16 May 2016 M3 L1 MIT Yes Details →
6.0.1 02 Apr 2016 M3 L1 MIT Yes Details →
6.0.0 10 Feb 2016 M3 L1 MIT Yes Details →
5.1.0 06 Jan 2016 M3 L1 MIT Yes Details →
5.0.3 04 Jan 2016 M3 L1 MIT Yes Details →
5.0.2 20 Nov 2015 M3 L1 MIT Yes Details →
5.0.1 30 Oct 2015 M3 L1 MIT Yes Details →
5.0.0 05 Oct 2015 M3 L1 MIT Yes Details →
4.4.0 18 Jul 2015 M3 L1 MIT Yes Details →
4.3.1 15 Jul 2015 M3 L1 MIT Yes Details →
4.3.0 29 Jun 2015 M3 L1 MIT Yes Details →
4.2.2 09 Jun 2015 M3 L1 MIT Yes Details →
4.2.1 01 May 2015 M3 L1 MIT Yes Details →
4.2.0 21 Apr 2015 M3 L1 MIT Yes Details →
4.1.2 19 Apr 2015 M3 L1 MIT Yes Details →
4.1.1 13 Apr 2015 M3 L1 MIT Yes Details →
4.1.0 31 Mar 2015 M3 L1 MIT Yes Details →
4.0.3 25 Mar 2015 M3 L1 MIT Yes Details →
4.0.2 22 Mar 2015 M3 L1 MIT Yes Details →
4.0.1 13 Mar 2015 M3 L1 MIT Yes Details →
4.0.0 12 Mar 2015 M3 L1 MIT Yes Details →
3.1.0 05 Mar 2015 M3 L1 MIT Yes Details →
3.0.7 22 Feb 2015 M3 L1 MIT Yes Details →
3.0.6 12 Feb 2015 M3 L1 MIT Yes Details →
3.0.5 06 Feb 2015 M3 L1 MIT Yes Details →
3.0.4 13 Jan 2015 M3 L1 MIT Yes Details →
3.0.3 11 Jan 2015 M3 L1 MIT Yes Details →
3.0.2 08 Jan 2015 M3 L1 MIT Yes Details →
3.0.1 07 Jan 2015 M3 L1 MIT Yes Details →
3.0.0 04 Jan 2015 M3 L1 MIT Yes Details →
2.2.1 29 Dec 2014 H1 M3 L1 MIT Yes Details →
2.2.0 28 Dec 2014 H1 M3 L1 MIT Yes Details →
2.1.3 24 Dec 2014 H1 M3 L1 MIT Yes Details →
2.1.2 23 Dec 2014 H1 M3 L1 MIT Yes Details →
2.1.1 22 Dec 2014 H1 M3 L1 MIT Yes Details →
2.1.0 21 Dec 2014 H1 M3 L1 MIT Yes Details →
2.0.0 19 Dec 2014 H1 M3 L1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2026 7

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

03 Vulnerabilities

Recorded vulnerabilities for markdown-it

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2015-10005: markdown-it - Inefficient Regular Expression Complexity 7.5 high 3.0.0 27 Dec 2022
CVE-2026-111759: markdown-it Quadratic Complexity in Smartquotes with Unmatched Closing Quotes 7.5 high 15.0.2 20 Oct 2026
CVE-2026-111758: markdown-it Quadratic-Time Rendering Vulnerability 7.5 high 14.3.3 20 Oct 2026
Performance Degradation in markdown-it due to Quadratic Complexity in linkify Handling 6.3 medium 15.0.1 29 Sep 2026
CVE-2022-21670: Uncontrolled Resource Consumption in markdown-it 5.3 medium 12.3.2 12 Jan 2022

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 markdown-it

Is markdown-it safe to use?

Vulert records 9 vulnerabilities for markdown-it in npm: 0 critical, 3 high, 5 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is markdown-it's Vulert package health score?

Vulert scores markdown-it 69/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).

Is the latest version of markdown-it affected?

No. 15.0.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of markdown-it should I use?

15.0.3 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 markdown-it have?

9 vulnerabilities are recorded for markdown-it in the npm ecosystem: 0 critical, 3 high, 5 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 markdown-it vulnerabilities disclosed?

7 vulnerabilities were recorded for markdown-it in the last 12 months, and the oldest entry in this database dates to 12 Jan 2022. 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 markdown-it 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 markdown-it for upcoming vulnerabilities?

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