VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

m2crypto: vulnerability history, versions and safety

m2crypto is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 59 releases, from Feb 2024 to Jul 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
2 with no fix published

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

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

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all m2crypto vulnerabilities

Vulert verdict on m2crypto 0.51.0 i

Updated on 23 Oct 2026

Careful: 0.51.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • 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 0.51.0 — affected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 5.9 i
  • With no published fix 2 i
  • Depended on by 51 packages i
  • Stars 56 i
  • Last release this month i
  • Licence BSD-2-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 m2crypto, 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
0.51.0 12 Oct 2026 M1 U1 BSD-2-Clause No Details →
0.50.0 09 Sep 2026 M1 U1 BSD-2-Clause No Details →
0.49.0 15 Aug 2026 M1 U1 BSD-2-Clause No Details →
0.48.0 23 May 2026 M1 U1 BSD-2-Clause No Details →
0.47.0 08 Feb 2026 M1 U1 BSD-2-Clause No Details →
0.46.2 02 Oct 2025 M1 U1 BSD-2-Clause No Details →
0.46.0 01 Oct 2025 M1 U1 BSD-2-Clause No Details →
0.45.1 23 Apr 2025 M1 U1 BSD-2-Clause No Details →
0.45.0 17 Apr 2025 M1 U1 BSD-2-Clause No Details →
0.44.0 17 Feb 2025 M1 U1 MIT No Details →
0.43.0 30 Oct 2024 M1 U1 MIT No Details →
0.42.0 10 Aug 2024 M1 U1 MIT No Details →
0.41.0 13 Feb 2024 M1 U1 MIT No Details →
0.40.1 25 Oct 2023 M1 U1 MIT No Details →
0.40.0 24 Oct 2023 M1 U1 MIT No Details →
0.39.0 04 Jul 2023 M1 U1 MIT No Details →
0.38.0 14 Jun 2021 M1 U1 MIT No Details →
0.37.1 08 Dec 2020 M1 U1 MIT No Details →
0.37.0 08 Dec 2020 M1 U1 MIT No Details →
0.36.0 13 Jul 2020 M1 U1 MIT No Details →
0.35.2 10 Jun 2019 M1 U1 MIT No Details →
0.35.1 08 Jun 2019 M1 U1 MIT No Details →
0.35.0 08 Jun 2019 M1 U1 MIT No Details →
0.34.0 30 May 2019 M1 U1 MIT No Details →
0.33.0 26 Apr 2019 M1 U1 MIT No Details →
0.32.0 04 Mar 2019 M1 U1 MIT No Details →
0.31.0 09 Nov 2018 M1 U1 MIT No Details →
0.30.1 29 Apr 2018 M1 U1 MIT No Details →
0.30.0 25 Apr 2018 M1 U1 MIT No Details →
0.29.0 23 Feb 2018 M1 U1 MIT No Details →
0.28.2 08 Feb 2018 M1 U1 MIT No Details →
0.28.1 08 Feb 2018 M1 U1 MIT No Details →
0.28.0 08 Feb 2018 M1 U1 MIT No Details →
0.27.0 05 Oct 2017 M1 U1 MIT No Details →
0.26.4 26 Sep 2017 M1 U1 non-standard No Details →
0.26.3 22 Sep 2017 M1 U1 non-standard No Details →
0.26.2 20 Sep 2017 M1 U1 non-standard No Details →
0.26.0 25 Mar 2017 M1 U1 non-standard No Details →
0.25.1 25 Jul 2016 M1 U1 non-standard No Details →
0.25.0 22 Jul 2016 M1 U1 non-standard No Details →
0.24.0 21 Mar 2016 M1 U1 non-standard No Details →
0.23.0 29 Jan 2016 M1 U1 non-standard No Details →
0.22.5 13 Oct 2015 M1 U1 non-standard No Details →
0.22.4 13 Oct 2015 M1 U1 non-standard No Details →
0.22.3 22 Jan 2014 M1 U1 non-standard No Details →
0.21.1 15 Jan 2011 M1 U1 non-standard No Details →
0.21.0 13 Jan 2011 M1 U1 non-standard No Details →
0.20.2 07 Oct 2009 M1 U1 non-standard No Details →
0.20.1 28 Aug 2009 M1 U1 non-standard No Details →
0.20.0 11 Aug 2009 M1 U1 non-standard No Details →
0.20.0b1 28 Jul 2009 M1 U1 non-standard No Details →
0.19.1 13 Oct 2008 M1 U1 non-standard No Details →
0.19.0 06 Oct 2008 M1 U1 non-standard No Details →
0.18.2 12 Oct 2007 M1 U1 — No Details →
0.18.1 08 Oct 2007 M1 U1 — No Details →
0.18.0 26 Jul 2007 M1 U1 — No Details →
0.17.0 21 Dec 2006 M1 U1 non-standard No Details →
0.16.0 05 Jul 2006 M1 U1 — No Details →
0.15.0 06 Apr 2006 M1 U1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for m2crypto

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-50781: m2crypto Bleichenbacher timing attack - incomplete fix 5.9 medium No fix published 05 Feb 2024
CVE-2023-50781: m2crypto Bleichenbacher Timing Attack - Incomplete Fix 5.9 medium No fix published 07 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 m2crypto

Is m2crypto safe to use?

Vulert records 2 vulnerabilities for m2crypto in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is m2crypto's Vulert package health score?

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

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

Which version of m2crypto should I use?

0.51.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 m2crypto have?

2 vulnerabilities are recorded for m2crypto 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 m2crypto vulnerabilities disclosed?

1 vulnerability was recorded for m2crypto in the last 12 months, and the oldest entry in this database dates to 05 Feb 2024. 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 m2crypto 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 m2crypto for upcoming vulnerabilities?

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