CVE-2024-26130: cryptography NULL pointer deference with pkcs12.serialize_key_and_certificates when called with a non-matching certificate and private key and an hmac_hash…
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.83% (FIRST EPSS); higher than 58% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: python3.12-cryptography (AlmaLinux:9) 41.0.7-2.el9_6.1; python-cryptography (Debian:12) 38.0.4-3+deb12u1; python-cryptography (Debian:13) 42.0.5-1.
Low priority for now. Upgrade to python3.12-cryptography (AlmaLinux:9) 41.0.7-2.el9_6.1; python-cryptography (Debian:12) 38.0.4-3+deb12u1; python-cryptography (Debian:13) 42.0.5-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 58th percentile
- CWE
- CWE-476
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| cryptography.io | cryptography | cpe:2.3:a:cryptography.io:cryptography |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
pyca cryptography
- >= 38.0.0, < 42.0.4affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cryptography.io cryptography38.0.0 and later · before 42.0.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | python3.12-cryptography | before 41.0.7-2.el9_6.1 | 41.0.7-2.el9_6.1 |
| Debian:12 | python-cryptography | before 38.0.4-3+deb12u1 | 38.0.4-3+deb12u1 |
| Debian:13 | python-cryptography | before 42.0.5-1 | 42.0.5-1 |
| openSUSE:Leap 15.5 | python-cryptography | before 41.0.3-150400.16.15.1 | 41.0.3-150400.16.15.1 |
| openSUSE:Leap 15.6 | python-cryptography | before 41.0.3-150600.23.3.1 | 41.0.3-150600.23.3.1 |
| openSUSE:Tumbleweed | python-cryptography | before 50.0.0-1.1 | 50.0.0-1.1 |
| openSUSE:Tumbleweed | python-cryptography | before 42.0.4-1.1 | 42.0.4-1.1 |
| PyPI | cryptography | from 38.0.0 · before 42.0.4 | 42.0.4 |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-black | before 0:22.8.0-2.el8ap | 0:22.8.0-2.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-cryptography | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-cryptography-debuginfo | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-idna | before 0:3.7-1.el8ap | 0:3.7-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-jinja2 | before 0:3.1.4-1.el8ap | 0:3.1.4-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-requests | before 0:2.32.2-1.el8ap | 0:2.32.2-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-black | before 0:22.8.0-2.el8ap | 0:22.8.0-2.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-cryptography | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-cryptography-debugsource | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-idna | before 0:3.7-1.el8ap | 0:3.7-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-jinja2 | before 0:3.1.4-1.el8ap | 0:3.1.4-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-requests | before 0:2.32.2-1.el8ap | 0:2.32.2-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptor | before 0:1.4.8-1.el8ap | 0:1.4.8-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptorctl | before 0:1.4.8-1.el8ap | 0:1.4.8-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-black | before 0:22.8.0-2.el9ap | 0:22.8.0-2.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-cryptography | before 0:42.0.5-1.el9ap | 0:42.0.5-1.el9ap |
+90
Same product
cryptography.io: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-36242In the cryptography package before 3.3.2 for Python, certain sequences of update calls to symmetrically encrypt multi-GB values could…38Monitor
- CVE-2026-26007cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves32Monitor
- CVE-2016-9243HKDF in cryptography before 1.5.2 returns an empty byte-string if used with a length less than algorithm.digest_size.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-38325Jul 14, 2023 · The cryptography package before 41.0.2 for Python mishandles SSH certificates that have critical options.30Monitor
- ← EarlierCVE-2023-49083Nov 29, 2023 · cryptography vulnerable to NULL-dereference when loading PKCS7 certificates30Monitor
- Later →CVE-2026-34073Mar 31, 2026 · cryptography has incomplete DNS name constraint enforcement on peer names6Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:python3.12-cryptography | 41.0.7-2.el9_6.1 · AlmaLinux:9 | Package registry (OSV) |
| debian:python-cryptography | 38.0.4-3+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:python-cryptography | 41.0.3-150400.16.15.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| PyPI:cryptography | 42.0.4 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.5.7-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python-cryptography | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python-cryptography-debugsource | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-cryptography | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-cryptography-debuginfo | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python39-cryptography | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python39-cryptography-debuginfo | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python39-pillow | 0:10.3.0-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python3x-cryptography | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python3x-cryptography-debugsource | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptor | 0:1.4.8-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptorctl | 0:1.4.8-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| rocky linux:python3.12-cryptography | 0:41.0.7-2.el9_6.1 · Rocky Linux:9 | Package registry (OSV) |
| suse:python-cryptography | 41.0.3-150400.16.15.1 · SUSE:Linux Enterprise Module for Python 3 15 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-4908384 days apartcryptography vulnerable to NULL-dereference when loading PKCS7 certificates30Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.