Cryptography vulnerabilitiesRanked by how likely they are to be used.
Cryptography is made by Cryptography.io. We track 8 published vulnerabilities in it, across 151 versions. None of them is on the list of flaws known to be exploited today. If you run Cryptography, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Cryptography vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Cryptography's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Cryptography flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 6.7%CVE-2020-36242Critical
In the cryptography package before 3.3.2 for Python, certain sequences of update calls to symmetrically encrypt multi-GB values could result in an integer overflow and buffer overflow, as demonstrated by the Fernet...
- 3.5%CVE-2016-9243High
HKDF in cryptography before 1.5.2 returns an empty byte-string if used with a length less than algorithm.digest_size.
- 2.5%CVE-2020-25659Medium
python-cryptography 3.2 is vulnerable to Bleichenbacher timing attacks in the RSA decryption API, via timed processing of valid PKCS#1 v1.5 ciphertext.
- 1.3%CVE-2023-23931Medium
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
- 1.1%CVE-2023-50782High
A flaw was found in the python-cryptography package.
- 1.0%CVE-2023-49083Medium
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
- 0.8%CVE-2024-26130High
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
- 0.7%CVE-2023-38325High
The cryptography package before 41.0.2 for Python mishandles SSH certificates that have critical options.
Running Cryptography? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
In the cryptography package before 3.3.2 for Python, certain sequences of update calls to symmetrically encrypt multi-GB values could result in an integer overflow and buffer overflow, as demonstrated by the Fernet class.
- Matched to
- Cryptography on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 8 published vulnerabilities listed under the name Cryptography, across 151 versions.
None of Cryptography's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Cryptography. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.