# CVE-2026-119170: Python hashlib FIPS algorithm enforcement regression

Source: https://junglewise.ai/threats/cve-2026-119170-there-was-a-regression-in-how-fips-algorithms-were-enforced-for  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-06. Updated: 2026-11-06  
License: CC BY 4.0 with a link back

CVE-2026-119170 · Severity: info · Published 2026-11-06

Python's cryptographic hash library (hashlib) contains a regression in how it enforces FIPS-approved algorithms when operating in FIPS mode. This affects only Python 3.14.10 when used with OpenSSL in FIPS mode. The regression could allow applications to use non-FIPS-compliant hashing functions when they should be restricted, potentially violating compliance requirements for security-sensitive deployments.

Technologies: [Python CPython](https://junglewise.ai/threats/technologies/python-cpython). Vendors: [Python](https://junglewise.ai/threats/vendors/python).

## Quick answers

**Is CVE-2026-119170 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-119170 being exploited in the wild.

**How severe is CVE-2026-119170?** Informational severity, published 6 November 2026.

**Which products and versions are affected?** Python CPython 3.14.10.

**Is there a fix for CVE-2026-119170?** Yes: fixed in Python 3.14 (patched on November 6, 2026). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-119170 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-119170?** Check whether you run Python CPython at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Python 3.14 (patched on November 6, 2026)

## Technical details

The vulnerability is a regression in the hashlib module's handling of the -fips property when usedforsecurity=True is specified. When OpenSSL operates in FIPS mode, only approved algorithms should be available; this bug caused incorrect enforcement of that restriction in Python 3.14.10. The fix requires proper application of the -fips property during algorithm selection.

## Affected products

- Python CPython 3.14.10

## Timeline

- 2026-10-29: disclosed
- 2026-11-06: patched

## References

- [https://github.com/python/cpython/issues/160923](https://github.com/python/cpython/issues/160923)
- [https://github.com/python/cpython/pull/160984](https://github.com/python/cpython/pull/160984)

## Related threats

- [Python http.cookies Morsel cookie attribute injection via unescaped semicolons](https://junglewise.ai/threats/cve-2026-16052-the-http-cookies-morsel-class-allows-separator-semicolons-in)
- [CPython ssl.get_server_certificate hostname verification bypass](https://junglewise.ai/threats/cve-2026-19552-when-ca-certs-parameter-was-supplied-to-ssl-get-server)
- [Python http.cookiejar cookie deletion policy bypass](https://junglewise.ai/threats/cve-2026-124249-http-cookiejar-cookiejar-deleted-a-stored-cookie-when-a-response)
- [Python socket.getaddrinfo() null byte truncation](https://junglewise.ai/threats/cve-2026-116566-socket-getaddrinfo-previously-accepted-null-bytes-within-host)
- [Python http.client HTTP response parsing bypass](https://junglewise.ai/threats/cve-2026-103995-response-body-and-chunk-parsing-would-handle-non-hex-or-negative)