Skip to content
Fencer Intel
high 7.5

CVE-2014-9601 json

Pillow denial of service via PNG bomb

published 2015-01-16 11 y ago modified 2026-06-17 4 mo ago also GHSA-h5rf-vgqx-wjv2 , PYSEC-2015-16 , EUVD-2015-0031

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
4.7%
EPSS 4.7% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

Pillow before 2.7.0 allows remote attackers to cause a denial of service via a compressed text chunk in a PNG image that has a large size when it is decompressed.

Patch / fix

  • pypi pillow 2.7.0
  • pillow Debian 14, Debian 13, Debian 12 2.6.1-2

debian advisories DEBIAN-CVE-2014-9601

  • pillow Ubuntu 14.04 LTS 2.3.0-1ubuntu3.4

ubuntu advisories UBUNTU-CVE-2014-9601

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-9601 updated cvss 2.6

python-pillow: potential denial-of-service during PNG decompression

  • Red Hat Enterprise Linux 5 python-imaging Red Hat Enterprise Linux 6 python-imaging, python-imaging-tk, python-imaging-sane Red Hat Enterprise Linux 7 python-pillow, python-pillow-qt, python-pillow-tk, python-pillow-sane
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.66% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi pillow
<2.7.0
2.7.0

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.