Is pycrypto safe to use?

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

What is pycrypto's Vulert package health score?

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

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

How many vulnerabilities does pycrypto have?

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

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

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

Vulnerability Database · PyPI · Package report

pycrypto: vulnerability history, versions and safety

pycrypto is a package in the PyPI ecosystem. Vulert records 8 vulnerabilities for it across 9 releases, from Jun 2012 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

8 vulnerabilities recorded C1 H2 M1 U4

3 with no fix published

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

See the unfixed vulnerabilities →

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pycrypto vulnerabilities

Vulert verdict on pycrypto 2.6.1 i

Updated on 23 Oct 2026

Careful: 2.6.1 has 6 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 Minor issues
Maintenance Slowing
Popularity Widely used
Community Not enough data

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 2.6.1 — affected i
Vulnerabilities on record 8 over 9 years · 0 in the last year i
Latest disclosure 17 May 2022 i
Highest CVSS 9.8 i
With no published fix 3 i
Depended on by 546 packages i
Last release 148 months ago i
Licence non-standard 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for pycrypto, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
2.6.1	20 Jun 2014	C1 H1 U2	non-standard	No	Details →
2.2.0	11 Aug 2013	C1 H2 M1 U4	—	No	Details →
2.1.0	11 Aug 2013	C1 H2 M1 U4	—	No	Details →
2.0.1	11 Aug 2013	C1 H2 M1 U4	non-standard	No	Details →
2.6.0	24 May 2012	C1 H2 U4	non-standard	No	Details →
2.5.0	13 Jan 2012	C1 H2 M1 U4	non-standard	No	Details →
2.4.1	04 Nov 2011	C1 H2 M1 U4	—	No	Details →
2.4.0	22 Oct 2011	C1 H2 M1 U4	—	No	Details →
2.3.0	17 Dec 2010	C1 H2 M1 U4	—	No	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

2012 1
2013 1
2017 1
2018 3
2022 2

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for pycrypto

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2013-7459: Buffer Overflow in pycrypto	9.8 critical	No fix published	14 Dec 2018
CVE-2018-6594: Weak ElGamal Key Parameters in PyCrypto	7.5 high	No fix published	12 Jul 2018
CVE-2013-1445: PyCrypto PRNG Reseeding Vulnerability	7.5 high	2.6.1	17 May 2022
CVE-2012-2417: PyCrypto makes Use of Insufficiently Random Values	5.3 medium	2.6	17 May 2022
CVE-2012-2417: PyCrypto ElGamal Key Generation Vulnerability	N/A unrated	9f912f13df99ad3421eff360d6a62d7dbec755c2	17 Jun 2012

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