How severe is CVE-2026-26007?

No CVSS score has been assigned to CVE-2026-26007 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-26007?

CVE-2026-26007 affects the following packages: cryptography (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-26007?

Update cryptography to 46.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26007 is resolved across your whole dependency graph.

How do I detect CVE-2026-26007 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cryptography, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-26007 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-26007 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-26007 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-26007?

CVE-2026-26007 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-26007?

CVE-2026-26007 is classified as CWE-345 (CWE-345), CWE-354 (CWE-354). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-26007 published, and has it been updated?

CVE-2026-26007 was published on February 10, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-26007 — cryptography

Fix: pyca/cryptography@0eebb9d

CVE-2026-26007 is a CWE-345 vulnerability in cryptography. A fix is available for cryptography — see the affected versions and patch details below.

cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves

Also known asGHSA-r6ph-v2qm-q3c2PYSEC-2026-2141

Published

Feb 10, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-26007.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍cryptography

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`cryptography`	all versions	46.0.5`pip install --upgrade 'cryptography==46.0.5'`

Affected Products

1 product · 1 configurations

Application

cryptographycryptography.io

< 46.0.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cryptography, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cryptography to 46.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26007 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This flaw, while difficult to exploit, would lead to a loss of integrity in the encrypted communication channel. Given that the cryptography package is a library, it is likely to be used in situations that do not require user interaction.

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2026-26007 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Ansible Automation Platform 2.5 for RHEL 8	`automation-controller-0:4.6.28-3.el8ap`	RHSA-2026:13512
Red Hat Enterprise Linux 8	`fence-agents-0:4.2.1-129.el8_10.25`	RHSA-2026:12176
Red Hat Enterprise Linux 9	`fence-agents-0:4.10.0-98.el9_7.12`	RHSA-2026:13672
Red Hat Enterprise Linux 9	`fence-agents-0:4.10.0-110.el9_8.2`	RHSA-2026:19355
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions	`fence-agents-0:4.10.0-43.el9_2.21`	RHSA-2026:22330
Red Hat Enterprise Linux 9.4 Extended Update Support	`fence-agents-0:4.10.0-62.el9_4.24`	RHSA-2026:21517
Red Hat Enterprise Linux 9.6 Extended Update Support	`fence-agents-0:4.10.0-86.el9_6.16`	RHSA-2026:21431
Red Hat Ansible Automation Platform 2.5	`ansible-automation-platform-25/lightspeed-rhel8:1777403872`	RHSA-2026:13553

UbuntuHIGH

USN-8087-1Ubuntu USN-8087-3Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-26007 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works