VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

cryptography: vulnerability history, versions and safety

cryptography is a package in the PyPI ecosystem. Vulert records 43 vulnerabilities for it across 120 releases, from Mar 2017 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
43 vulnerabilities recorded H12 M8 L5 U18
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
17 in the last 12 months

Most recent disclosure 04 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cryptography vulnerabilities

Vulert verdict on cryptography 50.0.2 i

Updated on 23 Oct 2026

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

Package health score 64/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • 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 50.0.2 — affected i
  • Vulnerabilities on record 43 over 9 years · 17 in the last year i
  • Latest disclosure 04 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 84,530 packages i
  • Stars 7,817 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence Apache-2.0 OR 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 cryptography, 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
50.0.2 30 Sep 2026 U2 Apache-2.0 OR BSD-3-Clause Yes Details →
50.0.1 25 Aug 2026 U2 Apache-2.0 OR BSD-3-Clause Yes Details →
50.0.0 31 Jul 2026 U2 Apache-2.0 OR BSD-3-Clause Yes Details →
49.0.0 12 Jun 2026 H1 U1 Apache-2.0 OR BSD-3-Clause Yes Details →
48.0.1 09 Jun 2026 H2 M1 U3 Apache-2.0 OR BSD-3-Clause Yes Details →
48.0.0 04 May 2026 H3 M1 U3 Apache-2.0 OR BSD-3-Clause Yes Details →
47.0.0 24 Apr 2026 H3 M1 U3 Apache-2.0 OR BSD-3-Clause Yes Details →
46.0.7 08 Apr 2026 H3 M1 U3 Apache-2.0 OR BSD-3-Clause Yes Details →
46.0.6 25 Mar 2026 H3 M2 U4 Apache-2.0 OR BSD-3-Clause Yes Details →
46.0.5 10 Feb 2026 H3 M2 L1 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
46.0.4 28 Jan 2026 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
46.0.3 15 Oct 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
46.0.2 01 Oct 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
46.0.1 17 Sep 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
46.0.0 16 Sep 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
45.0.7 01 Sep 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
45.0.6 05 Aug 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
45.0.5 02 Jul 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
45.0.4 10 Jun 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
45.0.3 25 May 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
45.0.2 18 May 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
45.0.1 17 May 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
45.0.0 17 May 2025 H4 M2 L1 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
44.0.3 02 May 2025 H4 M1 L1 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
44.0.2 02 Mar 2025 H4 M1 L1 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
44.0.1 11 Feb 2025 H4 M1 L1 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
44.0.0 27 Nov 2024 H4 M1 L2 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
43.0.3 18 Oct 2024 H3 M1 L2 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
43.0.1 03 Sep 2024 H3 M1 L2 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
43.0.0 20 Jul 2024 H3 M2 L2 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
42.0.8 04 Jun 2024 H3 M2 L2 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
42.0.7 06 May 2024 H3 M2 L2 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
42.0.6 04 May 2024 H3 M2 L2 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
42.0.5 24 Feb 2024 H3 M2 L2 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
42.0.4 21 Feb 2024 H3 M2 L2 U5 Apache-2.0 OR BSD-3-Clause Yes Details →
42.0.3 16 Feb 2024 H4 M2 L2 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
42.0.2 30 Jan 2024 H4 M2 L2 U6 Apache-2.0 OR BSD-3-Clause Yes Details →
42.0.1 25 Jan 2024 H4 M3 L2 U7 Apache-2.0 OR BSD-3-Clause Yes Details →
42.0.0 23 Jan 2024 H4 M3 L2 U7 Apache-2.0 OR BSD-3-Clause Yes Details →
41.0.7 28 Nov 2023 H5 M3 L1 U7 Apache-2.0 OR BSD-3-Clause Yes Details →
41.0.6 27 Nov 2023 H5 M3 L1 U7 Apache-2.0 OR BSD-3-Clause Yes Details →
41.0.5 24 Oct 2023 H5 M4 L1 U8 Apache-2.0 OR BSD-3-Clause Yes Details →
41.0.4 19 Sep 2023 H5 M4 L1 U8 Apache-2.0 OR BSD-3-Clause Yes Details →
41.0.3 01 Aug 2023 H5 M4 L2 U8 Apache-2.0 OR BSD-3-Clause Yes Details →
41.0.2 11 Jul 2023 H5 M4 L3 U8 Apache-2.0 OR BSD-3-Clause Yes Details →
41.0.1 01 Jun 2023 H6 M4 L3 U9 Apache-2.0 OR BSD-3-Clause Yes Details →
41.0.0 30 May 2023 H6 M4 L3 U9 Apache-2.0 OR BSD-3-Clause Yes Details →
40.0.2 14 Apr 2023 H6 M4 L4 U9 PSF-2.0 AND (Apache-2.0 OR BSD-3-Clause) Yes Details →
40.0.1 25 Mar 2023 H6 M4 L4 U9 PSF-2.0 AND (Apache-2.0 OR BSD-3-Clause) Yes Details →
40.0.0 24 Mar 2023 H6 M4 L4 U9 PSF-2.0 AND (Apache-2.0 OR BSD-3-Clause) Yes Details →
39.0.2 02 Mar 2023 H5 M4 L4 U8 PSF-2.0 AND (Apache-2.0 OR BSD-3-Clause) Yes Details →
39.0.1 07 Feb 2023 H5 M4 L4 U8 PSF-2.0 AND (Apache-2.0 OR BSD-3-Clause) Yes Details →
39.0.0 02 Jan 2023 H6 M6 L4 U10 PSF-2.0 AND (Apache-2.0 OR BSD-3-Clause) Yes Details →
38.0.4 27 Nov 2022 H6 M6 L4 U10 Apache-2.0 OR BSD-3-Clause Yes Details →
38.0.3 01 Nov 2022 H6 M6 L4 U10 Apache-2.0 OR BSD-3-Clause Yes Details →
38.0.2 11 Oct 2022 H6 M7 L4 U10 Apache-2.0 OR BSD-3-Clause Yes Details →
38.0.1 07 Sep 2022 H6 M7 L4 U10 Apache-2.0 OR BSD-3-Clause Yes Details →
38.0.0 07 Sep 2022 H6 M7 L4 U10 Apache-2.0 OR BSD-3-Clause Yes Details →
37.0.4 05 Jul 2022 H5 M7 L4 U9 Apache-2.0 OR BSD-3-Clause Yes Details →
37.0.3 21 Jun 2022 H5 M7 L4 U9 Apache-2.0 OR BSD-3-Clause Yes Details →
37.0.2 04 May 2022 H5 M7 L4 U9 Apache-2.0 OR BSD-3-Clause Yes Details →
37.0.1 27 Apr 2022 H5 M7 L4 U9 Apache-2.0 OR BSD-3-Clause Yes Details →
37.0.0 26 Apr 2022 H5 M7 L4 U9 Apache-2.0 OR BSD-3-Clause Yes Details →
36.0.2 15 Mar 2022 H5 M5 L4 U9 non-standard Yes Details →
36.0.1 14 Dec 2021 H5 M5 L4 U9 non-standard Yes Details →
36.0.0 21 Nov 2021 H5 M5 L4 U9 non-standard Yes Details →
35.0.0 30 Sep 2021 H5 M5 L4 U9 non-standard Yes Details →
3.4.8 24 Aug 2021 H5 M5 L4 U9 non-standard Yes Details →
3.4.7 25 Mar 2021 H5 M5 L4 U9 non-standard Yes Details →
3.4.6 16 Feb 2021 H5 M5 L4 U9 non-standard Yes Details →
3.4.5 13 Feb 2021 H5 M5 L4 U9 non-standard Yes Details →
3.4.4 09 Feb 2021 H5 M5 L4 U9 non-standard Yes Details →
3.4.3 09 Feb 2021 H5 M5 L4 U9 non-standard Yes Details →
3.4.2 08 Feb 2021 H5 M5 L4 U9 non-standard Yes Details →
3.4.1 07 Feb 2021 H5 M5 L4 U9 non-standard Yes Details →
3.4.0 07 Feb 2021 H5 M5 L4 U9 non-standard Yes Details →
3.3.2 07 Feb 2021 H5 M5 L4 U9 non-standard Yes Details →
3.3.1 10 Dec 2020 H6 M5 L4 U10 non-standard Yes Details →
3.3.0 09 Dec 2020 H6 M5 L4 U10 non-standard Yes Details →
3.2.1 28 Oct 2020 H6 M5 L4 U10 non-standard Yes Details →
3.2.0 26 Oct 2020 H6 M5 L4 U11 non-standard Yes Details →
3.1.1 22 Sep 2020 H7 M5 L4 U11 non-standard Yes Details →
3.1.0 27 Aug 2020 H7 M5 L4 U11 non-standard Yes Details →
3.0.0 20 Jul 2020 H6 M4 L4 U10 non-standard Yes Details →
2.9.2 22 Apr 2020 H6 M4 L4 U9 non-standard Yes Details →
2.9.1 21 Apr 2020 H6 M4 L4 U9 non-standard Yes Details →
2.9.0 02 Apr 2020 H6 M4 L4 U10 non-standard Yes Details →
2.8.0 17 Oct 2019 H6 M4 L4 U10 non-standard Yes Details →
2.7.0 31 May 2019 H6 M4 L4 U10 non-standard Yes Details →
2.6.1 27 Feb 2019 H6 M4 L4 U9 non-standard Yes Details →
2.6.0 27 Feb 2019 H6 M4 L4 U10 non-standard Yes Details →
2.5.0 22 Jan 2019 H6 M4 L4 U10 non-standard Yes Details →
2.4.2 21 Nov 2018 H6 M4 L3 U9 non-standard Yes Details →
2.4.1 12 Nov 2018 H6 M4 L3 U9 non-standard Yes Details →
2.4.0 12 Nov 2018 H6 M4 L3 U10 non-standard Yes Details →
2.3.1 14 Aug 2018 H6 M4 L3 U9 non-standard Yes Details →
2.3.0 18 Jul 2018 H6 M4 L3 U10 non-standard Yes Details →
2.2.2 27 Mar 2018 H7 M4 L3 U10 non-standard Yes Details →
2.2.1 21 Mar 2018 H7 M4 L3 U10 non-standard Yes Details →
2.2.0 19 Mar 2018 H7 M4 L3 U11 non-standard Yes Details →
2.1.4 30 Nov 2017 H7 M4 L3 U10 — Yes Details →
2.1.3 02 Nov 2017 H7 M4 L3 U10 — Yes Details →
2.1.2 24 Oct 2017 H7 M4 L3 U10 — Yes Details →
2.1.1 12 Oct 2017 H7 M4 L3 U10 — Yes Details →
2.1.0 11 Oct 2017 H7 M4 L3 U11 — Yes Details →
2.0.3 03 Aug 2017 H7 M4 L3 U10 — Yes Details →
2.0.2 27 Jul 2017 H7 M4 L3 U10 — Yes Details →
2.0.1 26 Jul 2017 H7 M4 L3 U10 — Yes Details →
2.0.0 17 Jul 2017 H7 M4 L3 U11 — Yes Details →
1.9.0 30 May 2017 H7 M4 L3 U11 — Yes Details →
1.8.2 26 May 2017 H6 M4 L3 U9 — Yes Details →
1.8.1 10 Mar 2017 H6 M4 L3 U9 — Yes Details →
1.8.0 10 Mar 2017 H6 M4 L3 U10 — Yes Details →
1.7.2 27 Jan 2017 H6 M3 L3 U8 — Yes Details →
1.7.1 13 Dec 2016 H6 M3 L3 U8 — Yes Details →
1.7.0 12 Dec 2016 H6 M3 L3 U10 — Yes Details →
1.6.0 22 Nov 2016 H6 M3 L3 U10 — Yes Details →
1.5.3 06 Nov 2016 H6 M3 L3 U8 — Yes Details →
1.5.2 26 Sep 2016 H7 M3 L3 U9 — Yes Details →
1.5.1 22 Sep 2016 H7 M3 L3 U9 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 2
  • 2020 1
  • 2021 3
  • 2022 2
  • 2023 11
  • 2024 5
  • 2025 1
  • 2026 17

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

03 Vulnerabilities

Recorded vulnerabilities for cryptography

The 5 most severe of 43 vulnerabilities recorded for this package

Search all 43 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-39892: Buffer Overflow Vulnerability in cryptography Package 9.8 critical 46.0.7 08 Apr 2026
CVE-2020-36242: Integer Overflow in cryptography Package 9.1 high 3.3.2 10 Feb 2021
CVE-2026-69249: python-cryptography Exponential Path-Building Vulnerability Due to Duplicate Self-Signed Intermediates 8.7 high 49.0.0 04 Aug 2026
CVE-2026-69249: python-cryptography Exponential Path-Building Vulnerability Due to Duplicate Self-Signed Intermediates 8.7 high 49.0.0 03 Aug 2026
CVE-2026-69247: Cryptography Package Exposes Bleichenbacher Oracle Through Distinguishable Errors and Timing 8.2 high 50.0.0 03 Aug 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 cryptography

Is cryptography safe to use?

Vulert records 43 vulnerabilities for cryptography in PyPI: 0 critical, 12 high, 8 medium and 5 low, plus 18 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 cryptography's Vulert package health score?

Vulert scores cryptography 64/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 cryptography affected?

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

Which version of cryptography should I use?

50.0.2 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 cryptography have?

43 vulnerabilities are recorded for cryptography in the PyPI ecosystem: 0 critical, 12 high, 8 medium and 5 low, plus 18 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 cryptography vulnerabilities disclosed?

17 vulnerabilities were recorded for cryptography in the last 12 months, and the oldest entry in this database dates to 27 Mar 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 cryptography 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 cryptography for upcoming vulnerabilities?

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