VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pycryptodome: vulnerability history, versions and safety

pycryptodome is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 53 releases, from Aug 2018 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
3 vulnerabilities recorded H1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 pycryptodome vulnerabilities

Vulert verdict on pycryptodome 4.1.0 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 4.1.0 — unaffected i
  • Vulnerabilities on record 3 over 7 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 6,158 packages i
  • Stars 3,277 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence BSD-2-Clause AND MIT AND Unlicense 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 pycryptodome, 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
4.1.0 19 Oct 2026 none BSD-2-Clause AND MIT AND Unlicense — Details →
4.0.1 17 Oct 2026 none BSD-2-Clause AND Unlicense — Details →
4.0.0 14 Oct 2026 none BSD-2-Clause AND Unlicense — Details →
3.24.1 11 Oct 2026 none non-standard — Details →
3.24.0 04 Oct 2026 none non-standard — Details →
3.23.0 17 May 2025 none non-standard — Details →
3.22.0 15 Mar 2025 none non-standard — Details →
3.21.0 02 Oct 2024 none non-standard — Details →
3.20.0 10 Jan 2024 none non-standard — Details →
3.19.1 28 Dec 2023 none non-standard — Details →
3.19.0 16 Sep 2023 U1 non-standard Yes Details →
3.18.0 19 May 2023 U1 non-standard Yes Details →
3.17.0 28 Jan 2023 U1 non-standard Yes Details →
3.16.0 26 Nov 2022 U1 non-standard Yes Details →
3.15.0 22 Jun 2022 U1 non-standard Yes Details →
3.14.1 04 Feb 2022 U1 non-standard Yes Details →
3.14.0 30 Jan 2022 U1 non-standard Yes Details →
3.13.0 23 Jan 2022 U1 non-standard Yes Details →
3.12.0 04 Dec 2021 U1 non-standard Yes Details →
3.11.0 08 Oct 2021 U1 non-standard Yes Details →
3.10.4 24 Sep 2021 U1 non-standard Yes Details →
3.10.3 24 Sep 2021 U1 non-standard Yes Details →
3.10.1 09 Feb 2021 U1 non-standard Yes Details →
3.9.9 02 Nov 2020 U1 non-standard Yes Details →
3.9.8 24 Jun 2020 U1 non-standard Yes Details →
3.9.7 21 Feb 2020 U1 non-standard Yes Details →
3.9.6 02 Feb 2020 U1 non-standard Yes Details →
3.9.4 18 Nov 2019 U1 non-standard Yes Details →
3.9.3 12 Nov 2019 U1 non-standard Yes Details →
3.9.2 10 Nov 2019 U1 non-standard Yes Details →
3.9.1 02 Nov 2019 U1 non-standard Yes Details →
3.9.0 28 Aug 2019 U1 non-standard Yes Details →
3.8.2 30 May 2019 U1 non-standard Yes Details →
3.8.1 04 Apr 2019 U1 non-standard Yes Details →
3.8.0 23 Mar 2019 U1 non-standard Yes Details →
3.7.3 20 Jan 2019 U1 non-standard Yes Details →
3.7.2 26 Nov 2018 U1 non-standard Yes Details →
3.7.1 25 Nov 2018 U1 non-standard Yes Details →
3.7.0 28 Oct 2018 U1 non-standard Yes Details →
3.6.6 17 Aug 2018 U1 non-standard Yes Details →
3.6.5 12 Aug 2018 H1 U2 non-standard Yes Details →
3.6.4 10 Jul 2018 H1 U2 non-standard Yes Details →
3.6.3 21 Jun 2018 H1 U2 non-standard Yes Details →
3.6.1 16 Apr 2018 H1 U2 non-standard Yes Details →
3.6.0 08 Apr 2018 H1 U2 non-standard Yes Details →
3.5.1 08 Mar 2018 H1 U2 non-standard Yes Details →
3.5.0 07 Mar 2018 H1 U2 non-standard Yes Details →
3.4.11 04 Feb 2018 H1 U2 non-standard Yes Details →
3.4.9 01 Feb 2018 H1 U2 non-standard Yes Details →
3.4.8 27 Jan 2018 H1 U2 non-standard Yes Details →
3.4.7 26 Aug 2017 H1 U2 non-standard Yes Details →
3.4.6 17 May 2017 H1 U2 non-standard Yes Details →
3.4.5 07 Feb 2017 H1 U2 non-standard Yes Details →
3.4.4 02 Feb 2017 H1 U2 non-standard Yes Details →
3.4.3 17 Oct 2016 H1 U2 non-standard Yes Details →
3.4.0 07 Feb 2016 H1 U2 non-standard Yes Details →
3.3.1 02 Nov 2015 H1 U2 non-standard Yes Details →
3.3.0 28 Oct 2015 H1 U2 non-standard Yes Details →
3.2.1 09 Sep 2015 H1 U2 non-standard Yes Details →
3.2.0 05 Sep 2015 H1 U2 non-standard Yes Details →
3.1.0 16 Mar 2015 H1 U2 non-standard Yes Details →
3.0.0 24 Jun 2014 H1 U2 non-standard Yes Details →
3.0.0rc1 14 Jun 2014 H1 U2 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for pycryptodome

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-15560: PyCryptodome Integer overflow vulnerability 7.5 high 3.6.6 27 Aug 2018
CVE-2023-52323: PyCryptodome and pycryptodomex OAEP Decryption Side-Channel Leakage 5.3 medium 3.19.1 07 Jul 2026
CVE-2018-15560: PyCryptodome Integer Overflow in AESNI.c N/A unrated 3.6.6 20 Aug 2018

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 pycryptodome

Is pycryptodome safe to use?

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

Vulert scores pycryptodome 84/100, which reads as in good shape. 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 pycryptodome affected?

No. 4.1.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.

How many vulnerabilities does pycryptodome have?

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

1 vulnerability was recorded for pycryptodome in the last 12 months, and the oldest entry in this database dates to 20 Aug 2018. 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 pycryptodome 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 pycryptodome for upcoming vulnerabilities?

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