CVE-2016-3076

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 36% 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
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 3%CVSS: 5.5Exploit: NoneExposed: 0

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

Heap-based buffer overflow in the j2k_encode_entry function in Pillow 2.5.0 through 3.1.1 allows remote attackers to cause a denial of service (memory corruption) via a crafted Jpeg2000 file.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
83.3%
KEV
Not listed

Published

April 24, 2017

Last Modified

May 13, 2026

Frequently asked(5)

What is CVE-2016-3076?
CVE-2016-3076 is a medium vulnerability published on April 24, 2017. Heap-based buffer overflow in the j2kencodeentry function in Pillow 2.5.0 through 3.1.1 allows remote attackers to cause a denial of service (memory corruption) via a crafted Jpeg2000 file.
When was CVE-2016-3076 disclosed?
CVE-2016-3076 was first published in the National Vulnerability Database on April 24, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-3076 actively exploited?
CVE-2016-3076 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-3076?
CVE-2016-3076 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2016-3076?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-3076, 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

Explore the affected products and dependency analysis for CVE-2016-3076

Explore →

Is Your Infrastructure Affected by CVE-2016-3076?

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