VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

markdown2: vulnerability history, versions and safety

markdown2 is a package in the PyPI ecosystem. Vulert records 8 vulnerabilities for it across 40 releases, from Jan 2018 to Apr 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded H1 M3 U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all markdown2 vulnerabilities

Vulert verdict on markdown2 2.5.5 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 2.5.5 — unaffected i
  • Vulnerabilities on record 8 over 4 years · 0 in the last year i
  • Latest disclosure 21 Apr 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 968 packages i
  • Stars 2,823 i
  • OpenSSF scorecard 3/10 i
  • Last release 7 months ago i
  • Licence MIT i
  • Similar names markdown i

Version list, release dates, licence and dependants published by PyPI, 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 markdown2, 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.5.5 02 Mar 2026 none MIT — Details →
2.5.4 27 Jul 2025 none MIT — Details →
2.5.3 24 Jan 2025 none MIT — Details →
2.5.2 11 Dec 2024 none MIT — Details →
2.5.1 09 Oct 2024 none MIT — Details →
2.5.0 11 Jul 2024 none MIT — Details →
2.4.13 25 Feb 2024 none MIT — Details →
2.4.12 17 Dec 2023 none MIT — Details →
2.4.11 03 Dec 2023 none MIT — Details →
2.4.10 25 Jul 2023 none MIT — Details →
2.4.9 22 Jun 2023 none MIT — Details →
2.4.8 12 Feb 2023 none MIT — Details →
2.4.7 22 Jan 2023 none MIT — Details →
2.4.6 20 Oct 2022 none MIT — Details →
2.4.5 25 Sep 2022 none MIT — Details →
2.4.4 25 Sep 2022 none MIT — Details →
2.4.3 27 Apr 2022 none MIT — Details →
2.4.2 02 Dec 2021 none MIT — Details →
2.4.1 18 Aug 2021 none MIT — Details →
2.4.0 22 Jan 2021 none MIT — Details →
2.3.10 19 Oct 2020 H1 U1 MIT Yes Details →
2.3.9 12 May 2020 H1 U1 MIT Yes Details →
2.3.8 29 May 2019 H1 M1 U2 MIT Yes Details →
2.3.7 05 Dec 2018 H1 M1 U2 MIT Yes Details →
2.3.6 26 Sep 2018 H1 M1 U2 MIT Yes Details →
2.3.5 10 Nov 2017 H1 M2 U3 MIT Yes Details →
2.3.4 26 Apr 2017 H1 M2 U3 MIT Yes Details →
2.3.3 04 Feb 2017 H1 M2 U3 MIT Yes Details →
2.3.2 30 Nov 2016 H1 M2 U3 MIT Yes Details →
2.3.1 19 Mar 2016 H1 M2 U3 MIT Yes Details →
2.3.0 18 Sep 2014 H1 M2 U3 MIT Yes Details →
2.2.3 03 Sep 2014 H1 M2 U3 MIT Yes Details →
2.2.2 19 Aug 2014 H1 M2 U3 MIT Yes Details →
2.2.1 07 Mar 2014 H1 M2 U3 MIT Yes Details →
2.2.0 02 Jan 2014 H1 M2 U3 MIT Yes Details →
2.1.0 18 Sep 2012 H1 M2 U3 MIT Yes Details →
2.0.1 18 Jul 2012 H1 M2 U3 MIT Yes Details →
2.0.0 15 Jun 2012 H1 M2 U3 MIT Yes Details →
1.4.2 27 Apr 2012 H1 M2 U3 MIT Yes Details →
1.4.1 27 Apr 2012 H1 M2 U3 MIT Yes Details →
1.4.0 20 Apr 2012 H1 M2 U3 MIT Yes Details →
1.3.1 12 Apr 2012 H1 M2 U3 MIT Yes Details →
1.3.0 05 Apr 2012 H1 M2 U3 MIT Yes Details →
1.2.0 04 Apr 2012 H1 M2 U3 MIT Yes Details →
1.1.1 01 Mar 2012 H1 M2 U3 MIT Yes Details →
1.1.0 01 Mar 2012 H1 M2 U3 MIT Yes Details →
1.0.1.19 19 Jul 2011 H1 M2 U3 MIT Yes Details →
1.0.1.18 08 Jul 2011 H1 M2 U3 MIT Yes Details →
1.0.1.17 27 May 2010 M2 U2 non-standard Yes Details →
1.0.1.16 16 Dec 2009 M2 U2 non-standard Yes Details →
1.0.1.15 30 Sep 2009 M2 U2 non-standard Yes Details →
1.0.1.14 29 Sep 2009 M2 U2 non-standard Yes Details →
1.0.1.13 02 Jul 2009 M3 U3 non-standard Yes Details →
1.0.1.12 04 Jun 2009 M3 U3 non-standard Yes Details →
1.0.1.11 01 Oct 2008 M3 U3 non-standard Yes Details →
1.0.1.10 18 Sep 2008 M3 U3 non-standard Yes Details →
1.0.1.9 12 Sep 2008 M3 U3 non-standard Yes Details →
1.0.1.8 10 Sep 2008 M3 U3 non-standard Yes Details →
1.0.1.7 09 Sep 2008 M3 U3 non-standard Yes Details →
1.0.1.6 09 Sep 2008 M3 U3 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2020 3
  • 2021 2
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for markdown2

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-26813: Vulnerability in markdown2 7.5 high 2.4.0 02 Jun 2021
CVE-2009-3724: Cross-site scripting in markdown2 for python 6.1 medium 1.0.1.14 21 Apr 2022
CVE-2020-11888: XSS in python-markdown2 6.1 medium 2.3.9 22 Apr 2020
CVE-2018-5773: markdown2 - Cross-Site Scripting Vulnerability 6.1 medium 2.3.6 12 Jul 2018
CVE-2018-5773: markdown2 - Cross-Site Scripting (XSS) Vulnerability N/A unrated 2.3.6 18 Jan 2018

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 markdown2

Is markdown2 safe to use?

Vulert records 8 vulnerabilities for markdown2 in PyPI: 0 critical, 1 high, 3 medium and 0 low, plus 4 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is markdown2's Vulert package health score?

Vulert scores markdown2 76/100, which reads as in good shape. 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 markdown2 affected?

No. 2.5.5, 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 markdown2 should I use?

2.5.5 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 markdown2 have?

8 vulnerabilities are recorded for markdown2 in the PyPI ecosystem: 0 critical, 1 high, 3 medium and 0 low, plus 4 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 markdown2 vulnerabilities disclosed?

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

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