Pillow vulnerabilitiesRanked by how likely they are to be used.
Pillow is made by Python. We track 54 published vulnerabilities in it, across 91 versions. None of them is on the list of flaws known to be exploited today. If you run Pillow, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Pillow vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Pillow's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Pillow flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 10%CVE-2014-3007Critical
Python Image Library (PIL) 1.1.7 and earlier and Pillow 2.3 might allow remote attackers to execute arbitrary commands via shell metacharacters in unspecified vectors related to CVE-2014-1932, possibly...
- 7.9%CVE-2016-4009Critical
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...
- 4.9%CVE-2021-27922High
Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICNS container, and thus an attempted memory...
- 4.6%CVE-2014-9601Medium
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.
- 4.2%CVE-2020-5311Critical
libImaging/SgiRleDecode.c in Pillow before 6.2.2 has an SGI buffer overflow.
- 4.0%CVE-2016-2533Medium
Buffer overflow in the ImagingPcdDecode function in PcdDecode.c in Pillow before 3.1.1 and Python Imaging Library (PIL) 1.1.7 and earlier allows remote attackers to cause a denial of service (crash) via a crafted...
- 3.7%CVE-2020-5312Critical
libImaging/PcxDecode.c in Pillow before 6.2.2 has a PCX P mode buffer overflow.
- 3.4%CVE-2014-3589Medium
PIL/IcnsImagePlugin.py in Python Imaging Library (PIL) and Pillow before 2.3.2 and 2.5.x before 2.5.2 allows remote attackers to cause a denial of service via a crafted block size.
- 3.3%CVE-2022-22817Critical
PIL.ImageMath.eval in Pillow before 9.0.0 allows evaluation of arbitrary expressions, such as ones that use the Python exec method.
- 3.2%CVE-2021-34552Critical
Pillow through 8.2.0 and PIL (aka Python Imaging Library) through 1.1.7 allow an attacker to pass controlled parameters directly into a convert function to trigger a buffer overflow in Convert.c.
Running Pillow? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Python Image Library (PIL) 1.1.7 and earlier and Pillow 2.3 might allow remote attackers to execute arbitrary commands via shell metacharacters in unspecified vectors related to CVE-2014-1932, possibly JpegImagePlugin.py.
- Matched to
- Pillow on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 54 published vulnerabilities listed under the name Pillow, across 91 versions.
None of Pillow's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Pillow. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.