VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mistune: vulnerability history, versions and safety

mistune is a package in the PyPI ecosystem. Vulert records 41 vulnerabilities for it across 57 releases, from Oct 2017 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
41 vulnerabilities recorded H8 M13 U20
i
3 with no fix published

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

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

Most recent disclosure 10 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mistune vulnerabilities

Vulert verdict on mistune 3.4.0 i

Updated on 23 Oct 2026

Careful: 3.4.0 has 4 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 Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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.4.0 — affected i
  • Vulnerabilities on record 41 over 8 years · 35 in the last year i
  • Latest disclosure 10 Sep 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 3 i
  • Depended on by 6,805 packages i
  • Stars 3,078 i
  • OpenSSF scorecard 4/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 mistune, 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.4.0 19 Oct 2026 H1 M2 U1 BSD-3-Clause No Details →
3.3.4 22 Jul 2026 H1 M2 U1 BSD-3-Clause No Details →
3.3.3 09 Jul 2026 H1 M2 U1 BSD-3-Clause No Details →
3.3.2 23 Jun 2026 H1 U1 BSD-3-Clause Yes Details →
3.3.1 22 Jun 2026 H1 U1 BSD-3-Clause Yes Details →
2.1.0 21 Jun 2026 H4 M6 U14 BSD-3-Clause Yes Details →
3.3.0 21 Jun 2026 H1 U1 BSD-3-Clause Yes Details →
3.2.1 03 May 2026 H4 M6 U10 BSD-3-Clause Yes Details →
3.2.0 23 Dec 2025 H6 M11 U16 BSD-3-Clause No Details →
3.1.4 29 Aug 2025 H5 M9 U16 BSD-3-Clause No Details →
3.1.3 19 Mar 2025 H5 M9 U16 BSD-3-Clause No Details →
3.1.2 19 Feb 2025 H5 M9 U16 BSD-3-Clause No Details →
3.1.1 28 Jan 2025 H5 M9 U16 BSD-3-Clause No Details →
3.1.0 30 Dec 2024 H5 M9 U16 BSD-3-Clause No Details →
3.0.2 29 Sep 2023 H5 M9 U16 BSD-3-Clause No Details →
3.0.1 09 Jun 2023 H5 M9 U16 BSD-3-Clause No Details →
3.0.0 08 Jun 2023 H5 M9 U16 BSD-3-Clause No Details →
3.0.0rc5 22 Mar 2023 H5 M9 U16 non-standard No Details →
2.0.5 07 Feb 2023 H4 M9 U15 BSD-3-Clause No Details →
3.0.0rc4 30 Nov 2022 H5 M9 U16 BSD-3-Clause No Details →
3.0.0rc3 25 Nov 2022 H5 M9 U16 BSD-3-Clause No Details →
3.0.0rc2 06 Nov 2022 H5 M9 U16 BSD-3-Clause No Details →
3.0.0rc1 26 Sep 2022 H5 M9 U16 BSD-3-Clause No Details →
2.0.4 14 Jul 2022 H4 M9 U15 BSD-3-Clause No Details →
3.0.0a3 14 Jul 2022 H5 M9 U16 BSD-3-Clause No Details →
3.0.0a2 12 Jul 2022 H5 M9 U16 BSD-3-Clause No Details →
3.0.0a1 12 Jul 2022 H5 M9 U16 BSD-3-Clause No Details →
2.0.3 27 Jun 2022 H4 M9 U15 BSD-3-Clause No Details →
2.0.2 14 Jan 2022 H5 M9 U16 BSD-3-Clause No Details →
2.0.1 30 Dec 2021 H5 M9 U16 BSD-3-Clause No Details →
2.0.0 05 Dec 2021 H5 M9 U16 BSD-3-Clause No Details →
2.0.0rc1 16 Feb 2021 H5 M9 U16 non-standard No Details →
2.0.0a6 26 Nov 2020 H5 M9 U16 non-standard No Details →
2.0.0a5 02 Sep 2020 H5 M9 U16 non-standard No Details →
2.0.0a4 19 Apr 2020 H5 M9 U16 non-standard No Details →
2.0.0a3 11 Apr 2020 H5 M9 U16 non-standard No Details →
2.0.0a2 01 Jan 2020 H5 M9 U16 non-standard No Details →
2.0.0a1 07 Dec 2019 H5 M9 U16 non-standard No Details →
0.8.4 11 Oct 2018 H4 M9 U15 non-standard No Details →
0.8.3 04 Dec 2017 H4 M9 U15 non-standard No Details →
0.8.2 04 Dec 2017 H4 M9 U15 non-standard No Details →
0.8.1 07 Nov 2017 H4 M9 U15 non-standard No Details →
0.8.0 26 Oct 2017 H4 M10 U16 non-standard No Details →
0.7.4 14 Mar 2017 H4 M11 U17 non-standard No Details →
0.7.3 29 Jun 2016 H4 M11 U17 non-standard No Details →
0.7.2 26 Feb 2016 H4 M11 U17 non-standard No Details →
0.7.1 22 Aug 2015 H4 M11 U17 non-standard No Details →
0.7.0 18 Jul 2015 H4 M11 U17 non-standard No Details →
0.6.0 17 Jun 2015 H4 M11 U17 non-standard No Details →
0.5.1 10 Mar 2015 H4 M11 U17 non-standard No Details →
0.5.0 05 Dec 2014 H4 M11 U17 non-standard No Details →
0.4.1 12 Oct 2014 H4 M11 U17 non-standard No Details →
0.4.0 14 Aug 2014 H4 M11 U17 non-standard No Details →
0.3.1 31 Jul 2014 H4 M11 U17 non-standard No Details →
0.3.0 27 Jun 2014 H4 M11 U17 non-standard No Details →
0.2.0 12 Mar 2014 H4 M11 U17 non-standard No Details →
0.1.0 26 Feb 2014 H4 M11 U17 non-standard No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2019 1
  • 2022 3
  • 2026 35

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

03 Vulnerabilities

Recorded vulnerabilities for mistune

The 5 most severe of 41 vulnerabilities recorded for this package

Search all 41 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-33079: Mistune ReDoS Vulnerability Leading to Denial of Service 8.7 high 3.2.1 13 Jul 2026
CVE-2022-34749: Mistune Catastrophic Backtracking Vulnerability 8.6 high 2.0.3 26 Jul 2022
CVE-2026-33441: Mistune Denial-of-Service Vulnerability 7.7 high 3.2.1 06 May 2026
CVE-2026-76098: Mistune Denial of Service via Excessive Emphasis Markers in Markdown 7.5 high 3.3.3 10 Sep 2026
CVE-2026-49851: Mistune Denial of Service via Quadratic-Time Parsing in parse_link_text 7.5 high 3.3.0 13 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 mistune

Is mistune safe to use?

Vulert records 41 vulnerabilities for mistune in PyPI: 0 critical, 8 high, 13 medium and 0 low, plus 20 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is mistune's Vulert package health score?

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

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

How many vulnerabilities does mistune have?

41 vulnerabilities are recorded for mistune in the PyPI ecosystem: 0 critical, 8 high, 13 medium and 0 low, plus 20 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 mistune vulnerabilities disclosed?

35 vulnerabilities were recorded for mistune in the last 12 months, and the oldest entry in this database dates to 19 Oct 2017. 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 mistune 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 mistune for upcoming vulnerabilities?

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