CVE-2012-1150

CVE-2012-1150 is a medium-severity vulnerability in Python with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-310.

Key facts

Description

Python before 2.6.8, 2.7.x before 2.7.3, 3.x before 3.1.5, and 3.2.x before 3.2.3 computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table.

Frequently asked questions

What is CVE-2012-1150?
Python before 2.6.8, 2.7.x before 2.7.3, 3.x before 3.1.5, and 3.2.x before 3.2.3 computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table.
How severe is CVE-2012-1150?
CVE-2012-1150 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2012-1150 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-1150?
CVE-2012-1150 primarily affects Python. In total, 58 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2012-1150?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2012-1150 published?
CVE-2012-1150 was published on 2012-10-05 and last updated on 2026-06-16.

References

Affected products (58)

More vulnerabilities in Python

All CVEs affecting Python →

Other CWE-310 (Cryptographic Issues) vulnerabilities

Browse all CWE-310 (Cryptographic Issues) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: