How severe is CVE-2024-26130?

CVE-2024-26130 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2024-26130 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-26130?

CVE-2024-26130 affects Cryptography.io Cryptography. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-26130?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-26130 have an EU (EUVD) identifier?

Yes. CVE-2024-26130 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-0031.

When was CVE-2024-26130 published?

CVE-2024-26130 was published on 2024-02-21 and last updated on 2026-06-17.

CVE-2024-26130

CVE-2024-26130 is a high-severity vulnerability in Cryptography.io Cryptography with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-476.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 1% (53rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-0031
Weakness: CWE-476
Affected product: Cryptography.io Cryptography
Published: 2024-02-21
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2024-26130?: 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.
How severe is CVE-2024-26130?: CVE-2024-26130 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2024-26130 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-26130?: CVE-2024-26130 affects Cryptography.io Cryptography. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-26130?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-26130 have an EU (EUVD) identifier?: Yes. CVE-2024-26130 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-0031.
When was CVE-2024-26130 published?: CVE-2024-26130 was published on 2024-02-21 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:cryptography.io:cryptography:*:*:*:*:*:python:*:*

More vulnerabilities in Cryptography.io Cryptography

CVE-2026-39892 — Critical (CVSS 9.8): cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. From 45.0.0 to…
CVE-2020-36242 — Critical (CVSS 9.1): In the cryptography package before 3.3.2 for Python, certain sequences of update calls to symmetrically encrypt…
CVE-2023-50782 — High (CVSS 7.5): A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured…
CVE-2023-38325 — High (CVSS 7.5): The cryptography package before 41.0.2 for Python mishandles SSH certificates that have critical options.
CVE-2016-9243 — High (CVSS 7.5): HKDF in cryptography before 1.5.2 returns an empty byte-string if used with a length less than algorithm.digest_size.
CVE-2026-26007 — Medium (CVSS 6.5): cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to…

All CVEs affecting Cryptography.io Cryptography →

Other CWE-476 (NULL Pointer Dereference) vulnerabilities

CVE-2022-36648 — Critical (CVSS 10.0): The hardware emulation in the of_dpa_cmd_add_l2_flood of rocker device model in QEMU, as used in 7.0.0 and earlier,…
CVE-2020-14500 — Critical (CVSS 10.0): Secomea GateManager all versions prior to 9.2c, An attacker can send a negative value and overwrite arbitrary data.
CVE-2010-2495 — Critical (CVSS 10.0): The pppol2tp_xmit function in drivers/net/pppol2tp.c in the L2TP implementation in the Linux kernel before 2.6.34 does…
CVE-2026-46195 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: smb: client: validate dacloffset before building…
CVE-2026-31657 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: batman-adv: hold claim backbone gateways by…
CVE-2026-31436 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: fix possible wrong descriptor…

Browse all CWE-476 (NULL Pointer Dereference) vulnerabilities →