CVE-2026-26007: CWE-345: Insufficient Verification of Data Authenticity in pyca cryptography
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.
AI Analysis
Technical Summary
The vulnerability in pyca cryptography (CVE-2026-26007) arises from missing validation that elliptic curve public key points belong to the prime-order subgroup of the curve. Functions such as public_key_from_numbers, EllipticCurvePublicNumbers.public_key(), load_der_public_key(), and load_pem_public_key() prior to version 46.0.5 do not perform this check. This allows an attacker to provide a public key point from a small-order subgroup, which can leak information about the victim's private key during ECDH shared secret computation or enable forgery of ECDSA signatures on the small subgroup. The issue specifically affects SECT curves with cofactor greater than 1. Red Hat's advisory notes the difficulty of exploitation but confirms potential loss of integrity in encrypted channels. While a fix exists in version 46.0.5, Red Hat currently does not provide a mitigation that meets their criteria for ease of use and deployment.
Potential Impact
Exploitation of this vulnerability can lead to leakage of private key bits during ECDH key exchange and allow forgery of ECDSA signatures on small subgroups, resulting in loss of integrity of encrypted communication channels. The vulnerability affects cryptographic operations relying on elliptic curve cryptography with SECT curves and cofactor > 1. Although exploitation is considered difficult, the impact is high due to potential compromise of cryptographic key material and signature integrity.
Mitigation Recommendations
A fix is available in cryptography package version 46.0.5 and later, which includes proper subgroup validation. Users should upgrade to version 46.0.5 or newer to remediate this vulnerability. Red Hat currently states that no alternative mitigation meeting their criteria is available. Therefore, applying the official patch is the recommended course of action.
CVE-2026-26007: CWE-345: Insufficient Verification of Data Authenticity in pyca cryptography
Description
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.
CVSS v4.0
Score 8.2high
Affected software
pyca
cryptography
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in pyca cryptography (CVE-2026-26007) arises from missing validation that elliptic curve public key points belong to the prime-order subgroup of the curve. Functions such as public_key_from_numbers, EllipticCurvePublicNumbers.public_key(), load_der_public_key(), and load_pem_public_key() prior to version 46.0.5 do not perform this check. This allows an attacker to provide a public key point from a small-order subgroup, which can leak information about the victim's private key during ECDH shared secret computation or enable forgery of ECDSA signatures on the small subgroup. The issue specifically affects SECT curves with cofactor greater than 1. Red Hat's advisory notes the difficulty of exploitation but confirms potential loss of integrity in encrypted channels. While a fix exists in version 46.0.5, Red Hat currently does not provide a mitigation that meets their criteria for ease of use and deployment.
Potential Impact
Exploitation of this vulnerability can lead to leakage of private key bits during ECDH key exchange and allow forgery of ECDSA signatures on small subgroups, resulting in loss of integrity of encrypted communication channels. The vulnerability affects cryptographic operations relying on elliptic curve cryptography with SECT curves and cofactor > 1. Although exploitation is considered difficult, the impact is high due to potential compromise of cryptographic key material and signature integrity.
Mitigation Recommendations
A fix is available in cryptography package version 46.0.5 and later, which includes proper subgroup validation. Users should upgrade to version 46.0.5 or newer to remediate this vulnerability. Red Hat currently states that no alternative mitigation meeting their criteria is available. Therefore, applying the official patch is the recommended course of action.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-09T21:36:29.552Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-26007","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:13512","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:12176","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:22330","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:21517","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:21431","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:13672","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:19355","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:6308","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:13553","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:13545","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:6309","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:2694","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:7295","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:10184","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:6568","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:6497","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:6567","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:5665","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:5168","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:22993","vendor":"Red Hat"}]
Threat ID: 698ba7284b57a58fa12c897a
Added to database: 02/10/2026, 21:46:16 UTC
Last enriched: 08/12/2026, 13:01:25 UTC
Last updated: 09/10/2026, 22:12:33 UTC
Views: 2303
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.