Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-26007: cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves

Noroxi assessment

Priority: Monitor (action score 32/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.39% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: pyca cryptography 46.0.5.

Low priority for now. Upgrade to pyca cryptography 46.0.5 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. 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.

HighCVSS 8.2 · v4.0—No exploit Fix available
Published
Feb 10, 2026
Updated
Sep 16, 2026
EPSS
0.3% · 33th percentile

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
32 / 40 · 8.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
8.2
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

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.

Follow CVE-2026-26007

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
cryptography.iocryptography

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • cryptography.io cryptographybefore 46.0.5

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

    • < 46.0.5affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8fence-agents-aliyunbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-allbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-amt-wsbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-apcbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-apc-snmpbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-awsbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-azure-armbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-bladecenterbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-brocadebefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-cisco-mdsbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-cisco-ucsbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-commonbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-computebefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-drac5before 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-eaton-snmpbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-emersonbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-epsbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-gcebefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-heuristics-pingbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-hpbladebefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-ibm-powervsbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-ibm-vpcbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-ibmbladebefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25
AlmaLinux:8fence-agents-ifmibbefore 4.2.1-129.el8_10.254.2.1-129.el8_10.25

+96

Other 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 result
    38Monitor
  • 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
  • CVE-2024-26130cryptography NULL pointer deference with pkcs12.serialize_key_and_certificates when called with a non-matching certificate and private key and an hmac_hash over
    30Monitor

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 certificates
    30Monitor
  • Later →CVE-2026-34073Mar 31, 2026 · cryptography has incomplete DNS name constraint enforcement on peer names
    6Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
pyca cryptography46.0.5 · descriptionVendor (CNA)
almalinux:fence-agents-aliyun4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-all4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-amt-ws4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-apc4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-apc-snmp4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-aws4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-azure-arm4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-bladecenter4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-brocade4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-cisco-mds4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-cisco-ucs4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
almalinux:fence-agents-common4.2.1-129.el8_10.25 · AlmaLinux:8Package registry (OSV)
alpine:py3-cryptography46.0.5-r0 · Alpine:v3.23Package registry (OSV)
debian:python-cryptography43.0.0-3+deb13u1 · Debian:13Package registry (OSV)
opensuse:oci-cli3.76.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python-cryptography46.0.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:cryptography46.0.5Package registry (OSV)
red hat:fence-agents0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-aliyun-debuginfo0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-all0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-amt-ws0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-apc0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-apc-snmp0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-azure-arm-debuginfo0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-bladecenter0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-brocade0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-cisco-mds0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-cisco-ucs0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:fence-agents-common0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)

+2

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records