# CVE-2024-26130: PYSEC-2024-225 - cryptography is a package designed to expose cryptographic primitives and recipes to Python…

Source: https://junglewise.ai/threats/cve-2024-26130-cryptography-null-pointer-dereference-with-pkcs12-serialize-key  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-02-21  
License: CC BY 4.0 with a link back

CVE-2024-26130 · Severity: low · CVSS 3.1 · Published 2024-02-21

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.

Technologies: [cryptography (PyPI)](https://junglewise.ai/threats/technologies/cryptography). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2024-26130 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-26130 being exploited in the wild.

**How severe is CVE-2024-26130?** Low severity, with a CVSS score of 3.1, published 21 February 2024.

**Which products and versions are affected?** cryptography (PyPI) ECOSYSTEM:introduced=38.0.0,fixed=42.0.4, GIT:introduced=0,fixed=97d231672763cdb5959a3b191e692a362f1b9e55|ECOSYSTEM:introduced=38.0.0,fixed=42.0.4.

**Is there a fix for CVE-2024-26130?** Yes. cryptography (PyPI): upgrade to 42.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2024-26130?** Check whether you run cryptography (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- cryptography (PyPI): upgrade to 42.0.4 or later

  ```sh
  pip install "cryptography>=42.0.4"
  ```


## Affected products

- cryptography (PyPI) ECOSYSTEM:introduced=38.0.0,fixed=42.0.4, GIT:introduced=0,fixed=97d231672763cdb5959a3b191e692a362f1b9e55|ECOSYSTEM:introduced=38.0.0,fixed=42.0.4

## Identifiers

- CVE-2024-26130
- GHSA-6vqw-3v5j-54x4
- PYSEC-2024-225

## Related threats

- [pyca cryptography improper certificate validation in Name Constraints](https://junglewise.ai/threats/cve-2026-69248-pyca-cryptography-improper-certificate-validation-in-name)
- [Pyca Cryptography exponential path-building in X.509 verification](https://junglewise.ai/threats/cve-2026-69249-pyca-cryptography-exponential-path-building-in-x-509-verification)
- [pyca cryptography Bleichenbacher oracle in PKCS#7 decryption](https://junglewise.ai/threats/cve-2026-69247-pyca-cryptography-bleichenbacher-oracle-in-pkcs-7-decryption)
- [PYSEC-2026-1284 - Vulnerable OpenSSL included in cryptography wheels](https://junglewise.ai/threats/cve-2024-12797-vulnerable-openssl-included-in-cryptography-wheels)
- [PYSEC-2026-1283 - Python Cryptography package vulnerable to Bleichenbacher timing oracle attack](https://junglewise.ai/threats/cve-2023-50782-python-cryptography-package-vulnerable-to-bleichenbacher-timing)