VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mpmath: vulnerability history, versions and safety

mpmath is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 60 releases, from Jun 2021 to Aug 2021. 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 H1 U1
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 mpmath vulnerabilities

Vulert verdict on mpmath 1.4.1 i

Updated on 23 Oct 2026

Action needed: 1.4.1 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 85/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 1.4.1 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 09 Aug 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 792 packages i
  • Stars 1,225 i
  • Last release 7 months ago i
  • Licence BSD-3-Clause 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 mpmath, 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
1.5.0a1 21 Aug 2026 U1 BSD-3-Clause Yes Details →
1.5.0a0 24 Jun 2026 U1 BSD-3-Clause Yes Details →
1.4.1 15 Mar 2026 U1 BSD-3-Clause Yes Details →
1.4.0 23 Feb 2026 U1 BSD-3-Clause Yes Details →
1.4.0b4 16 Feb 2026 U1 BSD-3-Clause Yes Details →
1.4.0b3 03 Jan 2026 U1 BSD-3-Clause Yes Details →
1.4.0b2 13 Oct 2025 U1 BSD-3-Clause Yes Details →
1.4.0b1 06 Sep 2025 U1 BSD-3-Clause Yes Details →
1.4.0a8 01 Sep 2025 U1 BSD-3-Clause Yes Details →
1.4.0a7 08 Aug 2025 U1 BSD-3-Clause Yes Details →
1.4.0a6 03 Jul 2025 U1 BSD-3-Clause Yes Details →
1.4.0a5 30 Apr 2025 U1 BSD-3-Clause Yes Details →
1.4.0a4 30 Jan 2025 U1 non-standard Yes Details →
1.4.0a3 22 Jan 2025 U1 non-standard Yes Details →
1.4.0a2 08 Oct 2024 U1 non-standard Yes Details →
1.4.0a1 16 Apr 2024 U1 non-standard Yes Details →
1.4.0a0 23 Feb 2024 U1 non-standard Yes Details →
1.3.0 07 Mar 2023 U1 non-standard Yes Details →
1.2.1 09 Feb 2021 H1 U1 non-standard Yes Details →
1.1.0 11 Dec 2018 H1 U1 non-standard Yes Details →
1.0.0 02 Oct 2017 H1 U1 non-standard Yes Details →
0.19.0 11 Jun 2014 H1 U1 non-standard Yes Details →
0.18.0 06 Jan 2014 H1 U1 non-standard Yes Details →
0.17.0 01 Feb 2011 H1 U1 non-standard Yes Details →
0.16.0 24 Sep 2010 H1 U1 non-standard Yes Details →
0.15.0 06 Jun 2010 H1 U1 non-standard Yes Details →
0.14.0 05 Feb 2010 H1 U1 non-standard Yes Details →
0.13.0 13 Aug 2009 H1 U1 non-standard Yes Details →
0.12.0 09 Jun 2009 H1 U1 non-standard Yes Details →
0.11.0 26 Jan 2009 H1 U1 non-standard Yes Details →
0.10.0 15 Oct 2008 H1 U1 non-standard Yes Details →
0.9.0 23 Aug 2008 H1 U1 non-standard Yes Details →
0.8.0 20 Apr 2008 H1 U1 non-standard Yes Details →
0.7.0 12 Mar 2008 H1 U1 non-standard Yes Details →
0.6.0 13 Jan 2008 H1 U1 non-standard Yes Details →
0.5.0 24 Nov 2007 H1 U1 non-standard Yes Details →
0.3.0 05 Oct 2007 H1 U1 non-standard Yes Details →
0.2.0 02 Oct 2007 H1 U1 non-standard Yes Details →
0.1.0 28 Sep 2007 H1 U1 non-standard Yes Details →
0.10.win32 — H1 U1 — Yes Details →
0.11.win32 — H1 U1 — Yes Details →
0.12.win32 — H1 U1 — Yes Details →
0.13.win32 — H1 U1 — Yes Details →
0.14.win32 — H1 U1 — Yes Details →
0.15.win32 — H1 U1 — Yes Details →
0.16.win32-py2.6 — H1 U1 — Yes Details →
0.17.win32 — H1 U1 — Yes Details →
0.2.win32 — H1 U1 — Yes Details →
0.3.win32 — H1 U1 — Yes Details →
0.4.src — H1 U1 non-standard Yes Details →
0.4.win32 — H1 U1 — Yes Details →
0.5.win32 — H1 U1 — Yes Details →
0.6.win32 — H1 U1 — Yes Details →
0.7.win32 — H1 U1 — Yes Details →
0.8.win32 — H1 U1 — Yes Details →
0.9.win32 — H1 U1 — Yes Details →
all-0.17 — H1 U1 non-standard Yes Details →
all-0.18 — H1 U1 non-standard Yes Details →
all-0.19 — H1 U1 non-standard Yes Details →
docsrc-0.16 — H1 U1 — 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

  • 2021 2

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

03 Vulnerabilities

Recorded vulnerabilities for mpmath

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-29063: ReDOS in Mpmath 7.5 high 1.3.0 09 Aug 2021
CVE-2021-29063: Regular Expression Denial of Service (ReDOS) in mpmath N/A unrated 46d44c3c8f3244017fe1eb102d564eb4ab8ef750 21 Jun 2021

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 mpmath

Is mpmath safe to use?

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

Vulert scores mpmath 85/100, which reads as healthy. 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 mpmath affected?

Yes. 1.4.1, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of mpmath should I use?

1.4.1 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 mpmath have?

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

0 vulnerabilities were recorded for mpmath in the last 12 months, and the oldest entry in this database dates to 21 Jun 2021. 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 mpmath 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 mpmath for upcoming vulnerabilities?

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