Integer overflow in the get_data function in zipimport.c in CPython (aka Python) before 2.7.12, 3.x before 3.4.5, and 3.5.x before 3.5.2 allows remote attackers to have unspecified impact via a negative data size value, which triggers a heap-based buffer overflow.
CVE-2016-5636
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 65(Track*)EG Risk 65/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation40% × 40%Automatability30% × 15%Action: Watch closely — could escalate to Attend. - EPSS
- 97.3%
- KEV
- Not listed
Published
September 2, 2016
Last Modified
May 6, 2026
Advisory Details (7)
Auto-updated May 9, 2026Issue 26171: heap overflow in zipimporter module - Python tracker
https://bugs.python.org/issue26171SP-CAAAPUE | Splunk Vulnerability Disclosure
http://www.splunk.com/view/SP-CAAAPUESP-CAAAPSV | Splunk Vulnerability Disclosure
http://www.splunk.com/view/SP-CAAAPSVoss-security - Re: CVE Request: heap overflow in Python zipimport module
http://www.openwall.com/lists/oss-security/2016/06/16/1oss-security - CVE Request: heap overflow in Python zipimport module
http://www.openwall.com/lists/oss-security/2016/06/15/15Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | python3.2-minimal (3.2.3-0ubuntu3.8) @ precise | 2026-05-20 | ubuntu |
| redhat | python-0:2.7.5-48.el7 | 2016-11-03 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
All Vendor Advisories
(2)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 11× in last 7d / 36× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 103 total refreshes for this CVE.
- 2026-07-23 14:14 UTCEPSS rescore
- 2026-07-23 01:23 UTCEG score recompute
- 2026-07-22 22:03 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-20 17:03 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-13 06:09 UTCEPSS rescore
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-11 08:23 UTCEPSS rescore
- 2026-07-09 19:05 UTCEPSS rescore
- 2026-07-08 15:10 UTCEPSS rescore
- 2026-07-08 07:27 UTCOSV refresh
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-28 14:04 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-27 03:05 UTCEPSS rescore
- 2026-06-27 03:05 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-22 14:23 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-19 19:25 UTCOSV refresh
- 2026-06-18 17:50 UTCEPSS rescore
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-15 17:45 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
- 2026-06-11 13:57 UTCEPSS rescore
- 2026-06-10 22:15 UTCEPSS rescore
- 2026-06-10 13:18 UTCEPSS rescore
- 2026-06-08 14:14 UTCEPSS rescore
- 2026-06-06 13:45 UTCEPSS rescore
- 2026-06-05 22:44 UTCEPSS rescore
- 2026-06-05 06:08 UTCEPSS rescore
- 2026-06-05 06:08 UTCEPSS rescore
- 2026-06-04 13:10 UTCEPSS rescore
- 2026-06-04 13:10 UTCEPSS rescore
- 2026-06-02 20:10 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-31 00:14 UTCEPSS rescore
- 2026-05-31 00:13 UTCOSV refresh
- 2026-05-29 13:41 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-21 22:40 UTCEPSS rescore
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-20 11:21 UTCEPSS rescore
- 2026-05-20 11:21 UTCEPSS rescore
- 2026-05-20 11:21 UTCEPSS rescore
- 2026-05-20 09:37 UTCVendor advisory
- 2026-05-20 09:37 UTCGHSA enrichment
- 2026-05-20 05:30 UTCVendor advisory
- 2026-05-20 05:30 UTCGHSA enrichment
- 2026-05-20 01:23 UTCVendor advisory
- 2026-05-20 01:23 UTCGHSA enrichment
- 2026-05-19 21:16 UTCVendor advisory
- 2026-05-19 21:16 UTCGHSA enrichment
- 2026-05-19 17:03 UTCVendor advisory
- 2026-05-19 17:03 UTCGHSA enrichment
- 2026-05-19 12:52 UTCVendor advisory
- 2026-05-19 12:52 UTCGHSA enrichment
- 2026-05-19 08:44 UTCVendor advisory
- 2026-05-19 08:44 UTCGHSA enrichment
- 2026-05-19 04:37 UTCVendor advisory
- 2026-05-19 04:37 UTCGHSA enrichment
- 2026-05-19 00:29 UTCEG score recompute
- 2026-05-19 00:29 UTCVendor advisory
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCinsuyun/CVE-2016-5636First seen Mar 28, 2016
CVE-2016-5636
Open source ↗
Frequently asked(5)
What is CVE-2016-5636?
When was CVE-2016-5636 disclosed?
Is CVE-2016-5636 actively exploited?
What is the CVSS score of CVE-2016-5636?
How do I remediate CVE-2016-5636?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2016-5636
Is Your Infrastructure Affected by CVE-2016-5636?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.