cryptography.io CVE Vulnerabilities & Metrics

Focus on cryptography.io vulnerabilities and metrics.

Last updated: 08 Mar 2026, 23:25 UTC

About cryptography.io Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with cryptography.io. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total cryptography.io CVEs: 9
Earliest CVE date: 27 Mar 2017, 17:59 UTC
Latest CVE date: 10 Feb 2026, 22:17 UTC

Latest CVE reference: CVE-2026-26007

Rolling Stats

30-day Count (Rolling): 1
365-day Count (Rolling): 1

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): 0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical cryptography.io CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 1.74

Max CVSS: 6.4

Critical CVEs (≥9): 0

CVSS Range vs. Count

Range Count
0.0-3.9 6
4.0-6.9 3
7.0-8.9 0
9.0-10.0 0

CVSS Distribution Chart

Top 5 Highest CVSS cryptography.io CVEs

These are the five CVEs with the highest CVSS scores for cryptography.io, sorted by severity first and recency.

All CVEs for cryptography.io

CVE-2026-26007 cryptography.io vulnerability CVSS: 0 10 Feb 2026, 22:17 UTC

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 46.0.5, the public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve. This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup. Only SECT curves are impacted by this. This vulnerability is fixed in 46.0.5.

CVE-2024-26130 cryptography.io vulnerability CVSS: 0 21 Feb 2024, 17:15 UTC

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Starting in version 38.0.0 and prior to version 42.0.4, if `pkcs12.serialize_key_and_certificates` is called with both a certificate whose public key did not match the provided private key and an `encryption_algorithm` with `hmac_hash` set (via `PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)`, then a NULL pointer dereference would occur, crashing the Python process. This has been resolved in version 42.0.4, the first version in which a `ValueError` is properly raised.

CVE-2023-50782 cryptography.io vulnerability CVSS: 0 05 Feb 2024, 21:15 UTC

A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

CVE-2023-49083 cryptography.io vulnerability CVSS: 0 29 Nov 2023, 19:15 UTC

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Calling `load_pem_pkcs7_certificates` or `load_der_pkcs7_certificates` could lead to a NULL-pointer dereference and segfault. Exploitation of this vulnerability poses a serious risk of Denial of Service (DoS) for any application attempting to deserialize a PKCS7 blob/certificate. The consequences extend to potential disruptions in system availability and stability. This vulnerability has been patched in version 41.0.6.

CVE-2023-38325 cryptography.io vulnerability CVSS: 0 14 Jul 2023, 20:15 UTC

The cryptography package before 41.0.2 for Python mishandles SSH certificates that have critical options.

CVE-2023-23931 cryptography.io vulnerability CVSS: 0 07 Feb 2023, 21:15 UTC

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since `update_into` was originally introduced in cryptography 1.8.

CVE-2020-36242 cryptography.io vulnerability CVSS: 6.4 07 Feb 2021, 20:15 UTC

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.

CVE-2020-25659 cryptography.io vulnerability CVSS: 4.3 11 Jan 2021, 16:15 UTC

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.

CVE-2016-9243 cryptography.io vulnerability CVSS: 5.0 27 Mar 2017, 17:59 UTC

HKDF in cryptography before 1.5.2 returns an empty byte-string if used with a length less than algorithm.digest_size.