CVE-2016-4009

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 5.3%, top 10% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 8%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Integer overflow in the ImagingResampleHorizontal function in libImaging/Resample.c in Pillow before 3.1.1 allows remote attackers to have unspecified impact via negative values of the new size, which triggers a heap-based buffer overflow.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
94.0%
KEV
Not listed

Published

April 13, 2016

Last Modified

May 6, 2026

Advisory Details (5)

Auto-updated May 8, 2026
No patch confirmed yet.
generic

Pillow: Multiple vulnerabilities (GLSA 201612-52) — Gentoo security

https://security.gentoo.org/glsa/201612-52
generic

Overflow in resample.c, with tests by wiredfool · Pull Request #1714 · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/pull/1714
generic

fix integer overflow in Resample.c · python-pillow/Pillow@4e0d9b0 · GitHub

https://github.com/python-pillow/Pillow/commit/4e0d9b0b9740d258ade40cce248c93777362ac1e
generic

Pillow/CHANGES.rst at c3cb690fed5d4bf0c45576759de55d054916c165 · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/blob/c3cb690fed5d4bf0c45576759de55d054916c165/CHANGES.rst
generic
http://www.securityfocus.com/bid/86064

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pillow1.0 ... 3.1.0rc1 (41 versions)3.1.1—

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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.

  1. 2026-07-11 08:23 UTCEPSS rescore
  2. 2026-07-09 19:05 UTCEPSS rescore
  3. 2026-07-08 15:10 UTCEPSS rescore
  4. 2026-07-08 09:05 UTCOSV refresh
  5. 2026-07-07 13:42 UTCEPSS rescore
  6. 2026-07-06 16:24 UTCEPSS rescore
  7. 2026-07-06 16:24 UTCEPSS rescore
  8. 2026-07-06 02:20 UTCEPSS rescore
  9. 2026-07-06 02:20 UTCEPSS rescore
  10. 2026-07-05 02:27 UTCEPSS rescore
  11. 2026-07-04 06:28 UTCEPSS rescore
  12. 2026-07-01 15:02 UTCEPSS rescore
  13. 2026-06-30 23:19 UTCEPSS rescore
  14. 2026-06-29 14:03 UTCEPSS rescore
  15. 2026-06-28 04:53 UTCEPSS rescore
  16. 2026-06-27 03:05 UTCEPSS rescore
  17. 2026-06-27 03:05 UTCEPSS rescore
  18. 2026-06-25 13:47 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-24 14:02 UTCEPSS rescore
  21. 2026-06-24 14:02 UTCEPSS rescore
  22. 2026-06-23 21:30 UTCEPSS rescore
  23. 2026-06-22 14:23 UTCEPSS rescore
  24. 2026-06-21 14:54 UTCEPSS rescore
  25. 2026-06-21 14:54 UTCEPSS rescore
Show 60 more
  1. 2026-06-21 01:57 UTCEPSS rescore
  2. 2026-06-21 01:57 UTCEPSS rescore
  3. 2026-06-19 21:06 UTCOSV refresh
  4. 2026-06-18 17:50 UTCEPSS rescore
  5. 2026-06-17 17:50 UTCEPSS rescore
  6. 2026-06-17 17:50 UTCEPSS rescore
  7. 2026-06-16 17:50 UTCEPSS rescore
  8. 2026-06-16 17:50 UTCEPSS rescore
  9. 2026-06-15 17:45 UTCEPSS rescore
  10. 2026-06-14 23:14 UTCEPSS rescore
  11. 2026-06-13 22:57 UTCEPSS rescore
  12. 2026-06-13 22:57 UTCEPSS rescore
  13. 2026-06-12 23:09 UTCEPSS rescore
  14. 2026-06-12 23:09 UTCEPSS rescore
  15. 2026-06-11 13:57 UTCEPSS rescore
  16. 2026-06-10 22:15 UTCEPSS rescore
  17. 2026-06-10 13:18 UTCEPSS rescore
  18. 2026-06-08 14:14 UTCEPSS rescore
  19. 2026-06-07 15:22 UTCEPSS rescore
  20. 2026-06-07 15:22 UTCEPSS rescore
  21. 2026-06-06 13:45 UTCEPSS rescore
  22. 2026-06-05 22:44 UTCEPSS rescore
  23. 2026-06-05 06:08 UTCEPSS rescore
  24. 2026-06-05 06:08 UTCEPSS rescore
  25. 2026-06-04 13:10 UTCEPSS rescore
  26. 2026-06-04 13:10 UTCEPSS rescore
  27. 2026-06-02 20:10 UTCEPSS rescore
  28. 2026-06-01 13:49 UTCEPSS rescore
  29. 2026-06-01 13:49 UTCEPSS rescore
  30. 2026-05-31 22:28 UTCEPSS rescore
  31. 2026-05-31 22:28 UTCEPSS rescore
  32. 2026-05-31 00:55 UTCOSV refresh
  33. 2026-05-31 00:14 UTCEPSS rescore
  34. 2026-05-29 13:41 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-27 13:38 UTCEPSS rescore
  39. 2026-05-26 13:42 UTCEPSS rescore
  40. 2026-05-26 07:16 UTCEPSS rescore
  41. 2026-05-24 16:43 UTCEPSS rescore
  42. 2026-05-23 00:10 UTCEG score recompute
  43. 2026-05-21 22:40 UTCEPSS rescore
  44. 2026-05-20 22:37 UTCEPSS rescore
  45. 2026-05-20 22:37 UTCEPSS rescore
  46. 2026-05-20 22:37 UTCEPSS rescore
  47. 2026-05-20 11:21 UTCEPSS rescore
  48. 2026-05-20 11:21 UTCEPSS rescore
  49. 2026-05-20 11:21 UTCEPSS rescore
  50. 2026-05-20 10:05 UTCEG score recompute
  51. 2026-05-20 05:57 UTCEG score recompute
  52. 2026-05-20 01:49 UTCEG score recompute
  53. 2026-05-19 21:41 UTCEG score recompute
  54. 2026-05-19 17:33 UTCEG score recompute
  55. 2026-05-19 13:25 UTCEG score recompute
  56. 2026-05-19 09:17 UTCEG score recompute
  57. 2026-05-19 05:10 UTCEG score recompute
  58. 2026-05-19 01:01 UTCEG score recompute
  59. 2026-05-18 21:30 UTCEPSS rescore
  60. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2016-4009?
CVE-2016-4009 is a critical vulnerability published on April 13, 2016. Integer overflow in the ImagingResampleHorizontal function in libImaging/Resample.c in Pillow before 3.1.1 allows remote attackers to have unspecified impact via negative values of the new size, which triggers a heap-based buffer overflow.
When was CVE-2016-4009 disclosed?
CVE-2016-4009 was first published in the National Vulnerability Database on April 13, 2016, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-4009 actively exploited?
CVE-2016-4009 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-4009?
CVE-2016-4009 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-4009?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-4009, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-4009

Explore →

Is Your Infrastructure Affected by CVE-2016-4009?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs