CVSS 4.0
8.2 highCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NCVE-2026-119170
High (8.2) in python software foundation cpython. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
On this page
There was a regression in how FIPS algorithms were enforced for the hashlib module. Only users that are using OpenSSL in FIPS mode are affected. Only Python 3.14.10 is affected, all other Python versions are unaffected.
Severity
- EPSS
- 0.5% estimated probability of exploitation activity in the next 30 days; 42nd percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-693 Protection Mechanism Failure
- OWASP Top 10
- A06:2025 Insecure Design
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-119170 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-119170?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-119170?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-119170 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
- python software foundation:cpython
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Python Software Foundation CPython | from 3.14.10 before 3.14.11 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | python3.14 | no fix listed | DEBIAN-CVE-2026-119170 |
| Ubuntu | 22.04:LTS | python3.10 | no fix listed | UBUNTU-CVE-2026-119170 |
| Ubuntu | 24.04:LTS | python3.12 | no fix listed | UBUNTU-CVE-2026-119170 |
| Ubuntu | 26.04:LTS, 26.10 | python3.14 | no fix listed | UBUNTU-CVE-2026-119170 |
| Ubuntu | Pro:14.04:LTS | python2.7, python3.4, python3.5 | no fix listed | UBUNTU-CVE-2026-119170 |
| Ubuntu | Pro:16.04:LTS | python2.7, python3.5 | no fix listed | UBUNTU-CVE-2026-119170 |
| Ubuntu | Pro:18.04:LTS | python2.7, python3.6, python3.7 and 1 more | no fix listed | UBUNTU-CVE-2026-119170 |
| Ubuntu | Pro:20.04:LTS | python2.7, python3.8, python3.9 | no fix listed | UBUNTU-CVE-2026-119170 |
| Ubuntu | Pro:22.04:LTS | python2.7, python3.11 | no fix listed | UBUNTU-CVE-2026-119170 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).