VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

markdown: vulnerability history, versions and safety

markdown is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 71 releases, first recorded in Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
1 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 05 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all markdown vulnerabilities

Vulert verdict on markdown 3.11.2 i

Updated on 23 Oct 2026

Careful: 3.11.2 has 1 known vulnerability, and 1 has 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 Sustainable
  • 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 3.11.2 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 05 Mar 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Depended on by 12,362 packages i
  • Stars 4,253 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by PyPI, 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, 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
3.11.2 19 Oct 2026 U1 BSD-3-Clause No Details →
3.11.1 13 Oct 2026 U1 BSD-3-Clause No Details →
3.11.0 25 Sep 2026 U1 BSD-3-Clause No Details →
3.10.3 30 Jul 2026 U1 BSD-3-Clause No Details →
3.10.2 09 Feb 2026 U1 BSD-3-Clause No Details →
3.10.1 21 Jan 2026 U1 BSD-3-Clause No Details →
3.10.0 03 Nov 2025 U1 BSD-3-Clause No Details →
3.9.0 04 Sep 2025 U1 BSD-3-Clause No Details →
3.8.2 19 Jun 2025 U1 BSD-3-Clause No Details →
3.8.1 18 Jun 2025 U1 BSD-3-Clause No Details →
3.8.0 11 Apr 2025 M1 U1 BSD-3-Clause No Details →
3.7.0 16 Aug 2024 M1 U1 non-standard No Details →
3.6.0 14 Mar 2024 M1 U1 non-standard No Details →
3.5.2 10 Jan 2024 M1 U1 non-standard No Details →
3.5.1 31 Oct 2023 M1 U1 non-standard No Details →
3.5.0 06 Oct 2023 M1 U1 non-standard No Details →
3.4.4 25 Jul 2023 M1 U1 non-standard No Details →
3.4.3 23 Mar 2023 M1 U1 non-standard No Details →
3.4.2 22 Mar 2023 M1 U1 non-standard No Details →
3.4.1 15 Jul 2022 M1 U1 non-standard No Details →
3.4.0 15 Jul 2022 M1 U1 non-standard No Details →
3.3.7 05 May 2022 M1 U1 non-standard No Details →
3.3.6 17 Nov 2021 M1 U1 non-standard No Details →
3.3.5 16 Nov 2021 M1 U1 non-standard No Details →
3.3.4 24 Feb 2021 M1 U1 non-standard No Details →
3.3.3 25 Oct 2020 M1 U1 non-standard No Details →
3.3.2 19 Oct 2020 M1 U1 non-standard No Details →
3.3.1 12 Oct 2020 M1 U1 non-standard No Details →
3.3.0 06 Oct 2020 M1 U1 non-standard No Details →
3.2.2 08 May 2020 M1 U1 non-standard No Details →
3.2.1 12 Feb 2020 M1 U1 non-standard No Details →
3.2.0 07 Feb 2020 M1 U1 non-standard No Details →
3.1.1 21 May 2019 M1 U1 non-standard No Details →
3.1.0 26 Mar 2019 M1 U1 non-standard No Details →
3.0.1 26 Sep 2018 M1 U1 non-standard No Details →
3.0.0 22 Sep 2018 M1 U1 non-standard No Details →
2.6.11 05 Jan 2018 M1 U1 non-standard No Details →
2.6.10 08 Dec 2017 M1 U1 non-standard No Details →
2.6.9 18 Aug 2017 M1 U1 non-standard No Details →
2.6.8 25 Jan 2017 M1 U1 non-standard No Details →
2.6.7 24 Sep 2016 M1 U1 non-standard No Details →
2.6.6 21 Mar 2016 M1 U1 non-standard No Details →
2.6.5 25 Nov 2015 M1 U1 non-standard No Details →
2.6.4 06 Nov 2015 M1 U1 non-standard No Details →
2.6.3 26 Oct 2015 M1 U1 non-standard No Details →
2.6.2 22 Apr 2015 M1 U1 non-standard No Details →
2.6.1 09 Mar 2015 M1 U1 non-standard No Details →
2.6.0 20 Feb 2015 M1 U1 non-standard No Details →
2.5.2 20 Nov 2014 M1 U1 non-standard No Details →
2.5.1 26 Sep 2014 M1 U1 non-standard No Details →
2.5.0 13 Sep 2014 M1 U1 non-standard No Details →
2.4.1 22 May 2014 M1 U1 non-standard No Details →
2.4.0 16 Feb 2014 M1 U1 non-standard No Details →
2.3.1 22 Mar 2013 M1 U1 non-standard No Details →
2.3.0 15 Mar 2013 M1 U1 non-standard No Details →
2.2.1 04 Nov 2012 M1 U1 non-standard No Details →
2.2.0 05 Jul 2012 M1 U1 non-standard No Details →
2.1.1 22 Jan 2012 M1 U1 non-standard No Details →
2.1.0 24 Nov 2011 M1 U1 non-standard No Details →
2.0.3 07 Oct 2009 M1 U1 non-standard No Details →
2.0.2 28 Sep 2009 M1 U1 non-standard No Details →
2.0.1 20 May 2009 M1 U1 non-standard No Details →
2.0.0 07 Apr 2009 M1 U1 non-standard No Details →
1.7.0 18 Feb 2008 M1 U1 non-standard No Details →
1.7.win32 — M1 U1 — No Details →
2.0.1.win32 — M1 U1 — No Details →
2.0.2.win32 — M1 U1 — No Details →
2.0.3.win32 — M1 U1 — No Details →
2.0.win32 — M1 U1 — No Details →
2.1.0.win32 — M1 U1 — No Details →
2.4.win-amd64 — M1 U1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for markdown

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-69534: Python-Markdown Denial of Service Vulnerability Due to Unhandled AssertionError 7.5 high No fix published 05 Mar 2026
CVE-2025-69534: Python-Markdown Uncaught Exception Leading to Denial of Service 5.5 medium 3.8.1 05 Mar 2026

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

Is markdown safe to use?

Vulert records 2 vulnerabilities for markdown in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is markdown's Vulert package health score?

Vulert scores markdown 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 markdown affected?

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

How many vulnerabilities does markdown have?

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

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

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