CVE-2026-26007: python-cryptography vulnerability
Affects python-cryptographySource GCVE Database
Not known to be exploited · CVSS 8.2 High · fixed in 1.2.3-1ubuntu0.3+esm3 : patch python-cryptography soon.
Data as of 27 Oct 2026, 06:42 UTC
- Patch
- Available – fixed in 1.2.3-1ubuntu0.3+esm3, 2.1.4-1ubuntu1.4+esm3, 2.8-3ubuntu0.3+esm2
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade the Ubuntu python-cryptography to 1.2.3-1ubuntu0.3+esm3 (package) or 2.1.4-1ubuntu1.4+esm3 (package) or 2.8-3ubuntu0.3+esm2 (package).
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu Pro 20.04 LTSpython-cryptographypkg:deb/ubuntu/python-cryptography?arch=source&distro=esm-infra/focalOther threats | Affected
| Fixed in
|
Ubuntu Pro 18.04 LTSpython-cryptographypkg:deb/ubuntu/python-cryptography?arch=source&distro=esm-infra/bionicOther threats | Affected
| Fixed in
|
Ubuntu Pro 16.04 LTSpython-cryptographypkg:deb/ubuntu/python-cryptography?arch=source&distro=esm-infra/xenialOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
USN-8087-1 fixed a vulnerability in python-cryptography. This update provides the corresponding update to Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. Original advisory details: It was discovered that python-cryptography incorrectly handled subgroup validation for SECT curves. A remote attacker could use this issue to perform a subgroup attack and possibly recover the least significant bits of private keys.