CVE-2026-26007

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 10, 2026

Last Modified

September 16, 2026

Advisory Details (10)

Auto-updated Jul 7, 2026
Patch available. Sources: github_commit, github, redhat.
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:19355
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:13672
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:13553
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:13545
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:13512
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:12176
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:10184
Web page

oss-security - PyCA cryptography 46.0.5 released with fix for CVE-2026-26007

http://www.openwall.com/lists/oss-security/2026/02/10/4
GitHub advisoryMentions a patch (unverified)

Subgroup Attack Due to Missing Subgroup Validation for SECT Curves · Advisory · pyca/cryptography · GitHub

https://github.com/pyca/cryptography/security/advisories/GHSA-r6ph-v2qm-q3c2
GitHub commit

commit 0eebb9dbb634 (pyca/cryptography)

Fix landed in pyca/cryptography commit 0eebb9dbb634 — awaiting tagged release

https://github.com/pyca/cryptography/commit/0eebb9dbb6343d9bc1d91e5a2482ed4e054a6d8c

Patch Availability(22)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
py3-cryptography—
  • every version up to 46.0.5-r0: fixed in 46.0.5-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
py3-cryptography—
  • every version up to 46.0.5-r0: fixed in 46.0.5-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography3.3.2-1 ... 49.0.0-1~exp1 (33 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography38.0.4-3 ... 49.0.0-2 (28 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography43.0.0-3
  • every version up to 43.0.0-3+deb13u1: fixed in 43.0.0-3+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography43.0.0-3 ... 46.0.1-1~exp1 (8 versions)
  • every version up to 46.0.5-1: fixed in 46.0.5-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
cryptography0.1 ... 46.0.4 (150 versions)
  • every version up to 46.0.5: fixed in 46.0.5
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 197 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 101 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-12 16:18 UTCEG score recompute
  5. 2026-10-11 20:00 UTCEG score recompute
  6. 2026-10-11 17:14 UTCEG score recompute
  7. 2026-10-11 14:45 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-10-06 04:45 UTCOSV refresh
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  24. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  25. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 28th percentile
Show 71 more
  1. 2026-09-16 12:21 UTCEG score recompute
  2. 2026-09-16 12:21 UTCVendor advisory
  3. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  4. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  6. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-09-10 13:23 UTCVendor advisory
  8. 2026-09-10 12:28 UTCEG score recompute
  9. 2026-09-10 12:28 UTCVendor advisory
  10. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  13. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  14. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  15. 2026-09-03 23:16 UTCOSV refresh
  16. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  18. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  19. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  20. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  21. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  23. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  24. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  25. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  26. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  27. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  28. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  29. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  30. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  31. 2026-08-17 12:22 UTCVendor advisory
  32. 2026-08-17 12:14 UTCEG score recompute
  33. 2026-08-17 12:14 UTCVendor advisory
  34. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  35. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  36. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  37. 2026-08-14 10:29 UTCEG score recompute
  38. 2026-08-14 10:29 UTCVendor advisory
  39. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  40. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  41. 2026-08-12 12:39 UTCVendor advisory
  42. 2026-08-12 12:14 UTCEG score recompute
  43. 2026-08-12 12:14 UTCVendor advisory
  44. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  45. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  46. 2026-08-09 15:11 UTCEG score recompute
  47. 2026-08-09 15:11 UTCVendor advisory
  48. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  49. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  50. 2026-08-07 22:16 UTCEG score recompute
  51. 2026-08-07 22:16 UTCVendor advisory
  52. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  53. 2026-08-06 04:03 UTCEG score recompute
  54. 2026-08-06 04:03 UTCVendor advisory
  55. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  56. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  57. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  58. 2026-08-02 20:55 UTCEG score recompute
  59. 2026-08-02 20:55 UTCVendor advisory
  60. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  61. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  62. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  63. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  64. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  65. 2026-07-27 12:42 UTCEG score recompute
  66. 2026-07-27 12:42 UTCVendor advisory
  67. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  68. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  69. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  70. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  71. 2026-07-23 03:07 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-26007?
CVE-2026-26007 is a medium-severity vulnerability; its CVE record was published on February 10, 2026. cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 46.0.5, the publickeyfromnumbers (or EllipticCurvePublicNumbers.publickey()), EllipticCurvePublicNumbers.publickey(), loadderpublickey() and loadpempublickey() functions do not verify…
When was the CVE record for CVE-2026-26007 published?
The CVE record for CVE-2026-26007 was published on February 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-26007 actively exploited?
CVE-2026-26007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-26007?
CVE-2026-26007 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-26007?
A fix for CVE-2026-26007 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-26007 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26007

Explore →

Is Your Infrastructure Affected by CVE-2026-26007?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.