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