Regression in FIPS enforcement of hash algorithms affecting only Python 3.14.10
Only affects CPython 3.14.10 when it runs OpenSSL in FIPS mode. The fix is in CPython 3.14.11.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.14.11
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.14.11.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A regression in Python's hashlib module fails to enforce FIPS-approved hash algorithms for installations that run OpenSSL in FIPS mode, and it affects only a single Python release. An attacker can remotely, without logging in and without any user action, alter data that relies on those hashes.
Read the original description
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.
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.2/10CVSS 8.2, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.14.11.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Python Software Foundation CPython
From 3.14.10 · fixed in 3.14.11
Evidence 3
- Advisory
- Patch
- Report
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119170
Is CVE-2026-119170 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A regression in how the hashlib module enforces FIPS-approved hash algorithms means some hash algorithms that should be blocked in FIPS mode may still be available. The advisory rates the issue HIGH severity.Source: mail.python.org
Which versions are affected by CVE-2026-119170?
CPython: from 3.14.10 before 3.14.11.Source: cve.now feed data
Am I affected, and how do I check?
Only CPython 3.14.10 is affected; the advisory says all other Python versions are unaffected. The issue only applies to Python builds using OpenSSL in FIPS mode. To check, look at the Python version reported by the interpreter and whether its OpenSSL is set up for FIPS mode.Source: mail.python.org
How do I fix CVE-2026-119170?
Upgrade from CPython 3.14.10 to CPython 3.14.11, which contains the fix.Source: mail.python.org