CVE-2026-26007

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

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.5(medium)
EPSS
26.3%
KEV
Not listed

Published

February 10, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Jul 7, 2026
Patch available. Sources: github_commit, github, redhat.
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:19355
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:13672
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:13553
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:13545
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:13512
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:12176
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:10184
generic

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 Patch Available

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

Vendor Advisories for CVE-2026-26007(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-cryptography (43.0.0-1ubuntu1.1) @ questing2026-06-12ubuntu
ubuntupython3-cryptography (1.2.3-1ubuntu0.3+esm3) @ xenial2026-06-12ubuntu
redhatsatellite/foreman-mcp-server-rhel9:17804920082026-06-03redhat
redhatfence-agents-0:4.10.0-43.el9_2.212026-06-01redhat
redhatfence-agents-0:4.10.0-62.el9_4.242026-05-28redhat
redhatfence-agents-0:4.10.0-86.el9_6.162026-05-27redhat
redhatfence-agents-0:4.10.0-110.el9_8.22026-05-19redhat
redhatfence-agents-0:4.10.0-98.el9_7.122026-05-05redhat
redhatautomation-controller-0:4.6.28-3.el9ap2026-05-04redhat
redhatansible-automation-platform-26/mcp-tools-rhel9:17773116012026-05-04redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17774038722026-05-04redhat
redhatfence-agents-0:4.2.1-129.el8_10.252026-04-30redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17763192752026-04-23redhat
redhatpython-cryptography-main-46.0.7-1.hum12026-04-09redhat
redhatquay/quay-rhel8:17751692192026-04-03redhat
redhatquay/quay-rhel9:17751692262026-04-03redhat
redhatquay/quay-rhel9:17750694912026-04-02redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17743630402026-04-01redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17744468742026-03-31redhat
redhatquay/quay-rhel8:17739710772026-03-24redhat
redhatquay/quay-rhel8:17739363232026-03-19redhat
redhatdiscovery/discovery-server-rhel9:17709135972026-02-12redhat

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
cryptography0.1 ... 46.0.4 (150 versions)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 13× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:22 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  7. 2026-07-13 22:30 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 15:15 UTCEPSS rescore
  15. 2026-07-08 15:15 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-07-01 15:06 UTCEPSS rescore
Show 64 more
  1. 2026-06-30 23:22 UTCEPSS rescore
  2. 2026-06-30 23:22 UTCEPSS rescore
  3. 2026-06-29 14:32 UTCOSV refresh
  4. 2026-06-29 14:06 UTCEPSS rescore
  5. 2026-06-28 14:07 UTCEPSS rescore
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 14:05 UTCEPSS rescore
  13. 2026-06-24 14:05 UTCEPSS rescore
  14. 2026-06-23 21:33 UTCEPSS rescore
  15. 2026-06-23 21:32 UTCEPSS rescore
  16. 2026-06-22 14:25 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 01:59 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-19 19:25 UTCEPSS rescore
  23. 2026-06-19 19:25 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-17 17:53 UTCEPSS rescore
  26. 2026-06-17 17:53 UTCEPSS rescore
  27. 2026-06-16 17:52 UTCEPSS rescore
  28. 2026-06-15 17:48 UTCEPSS rescore
  29. 2026-06-14 23:18 UTCEPSS rescore
  30. 2026-06-13 23:00 UTCEPSS rescore
  31. 2026-06-12 23:12 UTCEPSS rescore
  32. 2026-06-12 23:12 UTCEPSS rescore
  33. 2026-06-12 04:36 UTCEG score recompute
  34. 2026-06-12 04:36 UTCVendor advisory
  35. 2026-06-11 14:00 UTCEPSS rescore
  36. 2026-06-10 22:18 UTCEPSS rescore
  37. 2026-06-10 22:18 UTCEPSS rescore
  38. 2026-06-10 03:09 UTCEG score recompute
  39. 2026-06-10 03:09 UTCVendor advisory
  40. 2026-06-08 14:17 UTCEPSS rescore
  41. 2026-06-08 14:17 UTCEPSS rescore
  42. 2026-06-07 19:35 UTCEG score recompute
  43. 2026-06-07 19:35 UTCVendor advisory
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 15:25 UTCEPSS rescore
  46. 2026-06-07 15:25 UTCEPSS rescore
  47. 2026-06-06 13:47 UTCEPSS rescore
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-05 22:47 UTCEPSS rescore
  50. 2026-06-05 22:47 UTCEPSS rescore
  51. 2026-06-04 13:12 UTCEPSS rescore
  52. 2026-06-04 13:12 UTCEPSS rescore
  53. 2026-06-02 20:13 UTCEPSS rescore
  54. 2026-06-02 20:13 UTCEPSS rescore
  55. 2026-06-01 13:51 UTCEPSS rescore
  56. 2026-06-01 13:51 UTCEPSS rescore
  57. 2026-05-31 22:30 UTCEPSS rescore
  58. 2026-05-31 22:30 UTCEPSS rescore
  59. 2026-05-31 00:16 UTCEPSS rescore
  60. 2026-05-31 00:16 UTCEPSS rescore
  61. 2026-05-29 14:08 UTCEG score recompute
  62. 2026-05-29 14:08 UTCVendor advisory
  63. 2026-05-29 13:44 UTCEPSS rescore
  64. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-26007?
CVE-2026-26007 is a medium vulnerability 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 CVE-2026-26007 disclosed?
CVE-2026-26007 was first published in the National Vulnerability Database on February 10, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26007 actively exploited?
CVE-2026-26007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26007, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs