Cryptography

CVE-2026-119170

8.2

High

EPSS n/aPatch available

RCE in Python hashlib when OpenSSL is in FIPS mode on Python 3.14.10.

exploited

No known exploitation not in CISA KEV as of our last sync

fix

Patch available see the advisory in the references

likelihood

No EPSS score yet

Published 6 Nov 2026Analysed here 7 Nov 2026CVSS scored by the publisher (CNA)

common questions

Is CVE-2026-119170 being exploited?

Not confirmed. CVE-2026-119170 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-119170?

CVE-2026-119170 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-119170?

Yes. A fix has been recorded for CVE-2026-119170. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-119170 affect?

CVE-2026-119170 affects Python 3.14.10, CPython hashlib module, Systems using OpenSSL in FIPS mode. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-119170?

Upgrade Python 3.14.10 to the fixed release and apply the CPython security patch; avoid using OpenSSL FIPS mode until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary

technical analysis

affected

Python 3.14.10CPython hashlib moduleSystems using OpenSSL in FIPS mode

impact

Remote code execution on hosts running Python 3.14.10 with OpenSSL FIPS mode due to a hashlib FIPS-enforcement regression.

action required

Patch when possible

affected versions

Python Software Foundation CPython

affected>= 3.14.10 and < 3.14.11

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation: none
automatable: no
technical impact: total

Assessed by CISA 6 Nov 2026 (SSVC 2.0.3).

timeline

6 Nov 2026Published
6 Nov 2026CISA SSVC assessment: exploitation none · same day later
7 Nov 2026CVE record last updated · same day later
7 Nov 2026Analysed by vulneraibility.com · same day later

how to fix

Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.

references

NVD CVE.org CVE Details Source

4 references in the CVE record: 1 advisory, 1 patch, 2 links

Advisorymail.python.org /archives/list/[email protected]/thread/PXVTTOBPUMFJSSUXN6XCS7FC5DZOS
Patchgithub.com /python/cpython/pull/160984
Linkgithub.com /python/cpython/issues/160923
Linkopenwall.com /lists/oss-security/2026/11/06/30

sources

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free