VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pymdown-extensions: vulnerability history, versions and safety

pymdown-extensions is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 113 releases, from May 2023 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
10 vulnerabilities recorded H2 M2 L1 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
9 in the last 12 months

Most recent disclosure 10 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pymdown-extensions vulnerabilities

Vulert verdict on pymdown-extensions 12.3.0 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 12.3.0 — unaffected i
  • Vulnerabilities on record 10 over 3 years · 9 in the last year i
  • Latest disclosure 10 Aug 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 1,173 packages i
  • Stars 1,131 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT 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 pymdown-extensions, 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
12.3.0 14 Oct 2026 none MIT — Details →
12.2.0 10 Oct 2026 none MIT — Details →
12.1.0 23 Sep 2026 none MIT — Details →
12.0.1 15 Sep 2026 none MIT — Details →
12.0.0 15 Sep 2026 none MIT — Details →
11.0.2 22 Aug 2026 none MIT — Details →
11.0.1 02 Jul 2026 none MIT — Details →
11.0.0 23 Jun 2026 H1 U1 MIT Yes Details →
10.21.3 13 May 2026 H1 M1 U2 MIT Yes Details →
10.21.2 29 Mar 2026 H1 M2 U3 MIT Yes Details →
10.21.0 15 Feb 2026 H1 M2 U3 MIT Yes Details →
10.20.1 24 Jan 2026 H1 M2 U3 MIT Yes Details →
10.20.0 31 Dec 2025 H1 M2 U3 MIT Yes Details →
10.19.1 14 Dec 2025 H1 M2 U3 MIT Yes Details →
10.19.0 11 Dec 2025 H1 M2 U3 MIT Yes Details →
10.18.0 07 Dec 2025 H1 M2 U3 MIT Yes Details →
10.17.2 26 Nov 2025 H1 M2 U3 MIT Yes Details →
10.17.1 11 Nov 2025 H1 M2 U3 MIT Yes Details →
10.17.0 11 Nov 2025 H1 M2 U3 MIT Yes Details →
10.16.1 28 Jul 2025 H1 M2 U3 MIT Yes Details →
10.16.0 21 Jun 2025 H1 M2 L1 U4 MIT Yes Details →
10.15.0 27 Apr 2025 H1 M2 L1 U4 MIT Yes Details →
10.14.3 01 Feb 2025 H1 M2 L1 U4 MIT Yes Details →
10.14.2 29 Jan 2025 H1 M2 L1 U4 MIT Yes Details →
10.14.1 22 Jan 2025 H1 M2 L1 U4 MIT Yes Details →
10.14.0 07 Jan 2025 H1 M2 L1 U4 MIT Yes Details →
10.13.0 23 Dec 2024 H1 M2 L1 U4 MIT Yes Details →
10.12.0 29 Oct 2024 H1 M2 L1 U4 MIT Yes Details →
10.11.2 01 Oct 2024 H1 M2 L1 U4 MIT Yes Details →
10.11.1 29 Sep 2024 H1 M2 L1 U4 MIT Yes Details →
10.11.0 27 Sep 2024 H1 M2 L1 U4 MIT Yes Details →
10.10.2 26 Sep 2024 H1 M2 L1 U4 MIT Yes Details →
10.10.1 22 Sep 2024 H1 M2 L1 U4 MIT Yes Details →
10.10.0 22 Sep 2024 H1 M2 L1 U4 MIT Yes Details →
10.9.0 27 Jul 2024 H1 M2 L1 U4 MIT Yes Details →
10.8.1 27 Apr 2024 H1 M2 L1 U4 MIT Yes Details →
10.8.0 18 Apr 2024 H1 M2 L1 U4 MIT Yes Details →
10.7.1 05 Mar 2024 H1 M2 L1 U4 MIT Yes Details →
10.7.0 30 Dec 2023 H1 M2 L1 U4 MIT Yes Details →
10.6.0 27 Dec 2023 H1 M2 L1 U4 MIT Yes Details →
10.5.0 25 Nov 2023 H1 M2 L1 U4 MIT Yes Details →
10.4.0 10 Nov 2023 H1 M2 L1 U4 MIT Yes Details →
10.3.1 19 Oct 2023 H1 M2 L1 U4 MIT Yes Details →
10.3.0 02 Sep 2023 H1 M2 L1 U4 MIT Yes Details →
10.2.1 30 Aug 2023 H1 M2 L1 U4 MIT Yes Details →
10.2.0 28 Aug 2023 H1 M2 L1 U4 MIT Yes Details →
10.1.0 13 Jul 2023 H1 M2 L1 U4 MIT Yes Details →
10.0.1 16 May 2023 H1 M2 L1 U4 MIT Yes Details →
10.0.0 15 May 2023 H1 M1 L1 U3 MIT Yes Details →
9.11.0 07 Apr 2023 H2 M1 L1 U4 MIT Yes Details →
9.10.0 05 Mar 2023 H2 M1 L1 U4 MIT Yes Details →
9.10.0b5 02 Mar 2023 H2 M1 L1 U4 MIT Yes Details →
9.10.0b4 28 Feb 2023 H2 M1 L1 U4 MIT Yes Details →
9.10.0b3 25 Feb 2023 H2 M1 L1 U4 MIT Yes Details →
9.10.0b2 24 Feb 2023 H2 M1 L1 U4 MIT Yes Details →
9.10.0b1 22 Feb 2023 H2 M1 L1 U4 MIT Yes Details →
9.10.0a3 12 Feb 2023 H2 M1 L1 U4 MIT Yes Details →
9.9.2 20 Jan 2023 H2 M1 L1 U4 MIT Yes Details →
9.9.1 11 Jan 2023 H2 M1 L1 U4 MIT Yes Details →
9.10.0a2 17 Dec 2022 H2 M1 L1 U4 MIT Yes Details →
9.10.0a1 02 Dec 2022 H2 M1 L1 U4 MIT Yes Details →
9.9.0 23 Nov 2022 H2 M1 L1 U4 MIT Yes Details →
9.8.0 08 Nov 2022 H2 M1 L1 U4 MIT Yes Details →
9.7.0 22 Oct 2022 H2 M1 L1 U4 MIT Yes Details →
9.6.0 30 Sep 2022 H2 M1 L1 U4 MIT Yes Details →
9.5.0 06 Jun 2022 H2 M1 L1 U4 MIT Yes Details →
9.4.0 25 Apr 2022 H2 M1 L1 U4 MIT Yes Details →
9.3.0 19 Mar 2022 H2 M1 L1 U4 MIT Yes Details →
9.2.0 11 Feb 2022 H2 M1 L1 U4 MIT Yes Details →
9.1.0 14 Nov 2021 H2 M1 L1 U4 MIT Yes Details →
9.0.0 29 Sep 2021 H2 M1 L1 U4 MIT Yes Details →
9.0.0.dev0 29 Sep 2021 H2 M1 L1 U4 MIT Yes Details →
8.2.0 08 May 2021 H2 M1 L1 U4 MIT Yes Details →
8.1.1 26 Jan 2021 H2 M1 L1 U4 MIT Yes Details →
8.1.0 24 Dec 2020 H2 M1 L1 U4 MIT Yes Details →
8.0.1 28 Sep 2020 H2 M1 L1 U4 MIT Yes Details →
8.0.0 11 Aug 2020 H2 M1 L1 U4 MIT Yes Details →
7.1.0 18 Apr 2020 H2 M1 L1 U4 MIT Yes Details →
7.0.0 07 Apr 2020 H2 M1 L1 U4 MIT Yes Details →
7.0.0rc2 30 Mar 2020 H2 M1 L1 U4 MIT Yes Details →
7.0.0rc1 19 Mar 2020 H2 M1 L1 U4 MIT Yes Details →
7.0.0b2 20 Feb 2020 H2 M1 L1 U4 MIT Yes Details →
7.0.0b1 13 Feb 2020 H2 M1 L1 U4 MIT Yes Details →
6.3.0 07 Feb 2020 H2 M1 L1 U4 MIT Yes Details →
6.2.1 22 Dec 2019 H2 M1 L1 U4 MIT Yes Details →
6.2.0 16 Nov 2019 H2 M1 L1 U4 MIT Yes Details →
6.1.0 01 Sep 2019 H2 M1 L1 U4 MIT Yes Details →
6.0.0 09 Oct 2018 H2 M1 L1 U4 MIT Yes Details →
5.0.0 18 Aug 2018 H2 M1 L1 U4 MIT Yes Details →
4.12.0 21 Jul 2018 H2 M1 L1 U4 MIT Yes Details →
4.11.0 10 Jun 2018 H2 M1 L1 U4 MIT Yes Details →
4.10.2 17 May 2018 H2 M1 L1 U4 MIT Yes Details →
4.10.1 30 Apr 2018 H2 M1 L1 U4 MIT Yes Details →
4.10.0 19 Apr 2018 H2 M1 L1 U4 MIT Yes Details →
4.9.2 27 Mar 2018 H2 M1 L1 U4 MIT Yes Details →
4.9.1 18 Mar 2018 H2 M1 L1 U4 MIT Yes Details →
4.9.0 03 Mar 2018 H2 M1 L1 U4 MIT Yes Details →
4.8.0 18 Jan 2018 H2 M1 L1 U4 MIT Yes Details →
4.7.0 09 Dec 2017 H2 M1 L1 U4 MIT Yes Details →
4.6.0 02 Dec 2017 H2 M1 L1 U4 MIT Yes Details →
4.5.1 29 Nov 2017 H2 M1 L1 U4 — Yes Details →
4.5.0 26 Nov 2017 H2 M1 L1 U4 — Yes Details →
4.4.0 23 Nov 2017 H2 M1 L1 U4 — Yes Details →
4.3.0 15 Nov 2017 H2 M1 L1 U4 — Yes Details →
4.2.0 13 Nov 2017 H2 M1 L1 U4 — Yes Details →
4.1.0 12 Oct 2017 H2 M1 L1 U4 — Yes Details →
4.0.0 30 Aug 2017 H2 M1 L1 U4 — Yes Details →
3.5.0 14 Jun 2017 H2 M1 L1 U4 — Yes Details →
3.4.0 02 Jun 2017 H2 M1 L1 U4 — Yes Details →
3.3.0 27 May 2017 H2 M1 L1 U4 — Yes Details →
3.2.1 23 May 2017 H2 M1 L1 U4 — Yes Details →
3.2.0 16 May 2017 H2 M1 L1 U4 — Yes Details →
3.1.0 07 May 2017 H2 M1 L1 U4 — Yes Details →
3.0.0 16 Apr 2017 H2 M1 L1 U4 — Yes Details →
2.0.0 12 Feb 2017 H2 M1 L1 U4 — Yes Details →
1.8.0 28 Jan 2017 H2 M1 L1 U4 — Yes Details →
1.7.0 21 Jan 2017 H2 M1 L1 U4 — Yes Details →
1.6.1 17 Jan 2017 H2 M1 L1 U4 — Yes Details →
1.6.0 16 Jan 2017 H2 M1 L1 U4 — Yes Details →
1.5.0 13 Jan 2017 H2 M1 L1 U4 — Yes Details →

The newest 120 of 126 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2025 1
  • 2026 8

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

03 Vulnerabilities

Recorded vulnerabilities for pymdown-extensions

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-32309: Arbitrary File Inclusion in pymdown-extensions 7.5 high 10.0 15 May 2023
CVE-2023-32309: pymdown-extensions Arbitrary File Inclusion Vulnerability 7.5 high 10.0 07 Jul 2026
CVE-2026-67422: pymdown-extensions Exponential Backtracking ReDoS in Inline Processors 7.5 high 11.0.1 07 Aug 2026
CVE-2026-67422: pymdown-extensions Exponential Backtracking ReDoS in Inline Processors 7.5 high 11.0.1 10 Aug 2026
CVE-2026-61632: Path Traversal Vulnerability in PyMdown Extensions Allows Unauthorized File Access 5.3 medium 11.0.0 24 Jul 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 pymdown-extensions

Is pymdown-extensions safe to use?

Vulert records 10 vulnerabilities for pymdown-extensions in PyPI: 0 critical, 2 high, 2 medium and 1 low, plus 5 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 pymdown-extensions's Vulert package health score?

Vulert scores pymdown-extensions 65/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 pymdown-extensions affected?

No. 12.3.0, 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 pymdown-extensions should I use?

12.3.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 pymdown-extensions have?

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

9 vulnerabilities were recorded for pymdown-extensions in the last 12 months, and the oldest entry in this database dates to 15 May 2023. 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 pymdown-extensions 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 pymdown-extensions for upcoming vulnerabilities?

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