Vulnerability Database · PyPI · Package report

pillow: vulnerability history, versions and safety

pillow is a package in the PyPI ecosystem. Vulert records 196 vulnerabilities for it across 120 releases, from Apr 2014 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
196 vulnerabilities recorded C15 H74 M27 L1 U79
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
80 in the last 12 months

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on pillow 13.0.0 i

Updated on 23 Oct 2026

Action needed: 13.0.0 has 8 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 66/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 13.0.0 — affected i
  • Vulnerabilities on record 196 over 12 years · 80 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 89,616 packages i
  • Stars 13,912 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence MIT-CMU i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for pillow, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
13.0.0 16 Oct 2026 U8 MIT-CMU Yes Details →
12.3.0 01 Jul 2026 C4 H23 M12 MIT-CMU Yes Details →
12.2.0 01 Apr 2026 C4 H33 M15 U13 MIT-CMU Yes Details →
12.1.1 11 Feb 2026 C4 H35 M18 U18 MIT-CMU Yes Details →
12.1.0 02 Jan 2026 C4 H36 M18 U19 MIT-CMU Yes Details →
12.0.0 15 Oct 2025 C4 H36 M18 U19 MIT-CMU Yes Details →
11.3.0 01 Jul 2025 C4 H35 M17 U18 MIT-CMU Yes Details →
11.2.1 12 Apr 2025 C4 H36 M16 U19 MIT-CMU Yes Details →
11.1.0 02 Jan 2025 C4 H35 M15 U17 MIT-CMU Yes Details →
11.0.0 15 Oct 2024 C4 H34 M15 U17 MIT-CMU Yes Details →
10.4.0 01 Jul 2024 C3 H33 M15 U17 HPND Yes Details →
10.3.0 01 Apr 2024 C3 H33 M15 U17 HPND Yes Details →
10.2.0 02 Jan 2024 C3 H31 M15 U15 HPND Yes Details →
10.1.0 15 Oct 2023 C4 H32 M15 U16 HPND Yes Details →
10.0.1 15 Sep 2023 C4 H32 M15 U16 HPND Yes Details →
10.0.0 01 Jul 2023 C4 H33 M15 U18 HPND Yes Details →
9.5.0 01 Apr 2023 C4 H33 M15 U19 HPND Yes Details →
9.4.0 02 Jan 2023 C4 H33 M15 U19 HPND Yes Details →
9.3.0 29 Oct 2022 C4 H32 M15 U19 HPND Yes Details →
9.2.0 01 Jul 2022 C4 H33 M15 U22 HPND Yes Details →
9.1.1 17 May 2022 C4 H32 M14 U22 HPND Yes Details →
9.1.0 01 Apr 2022 C4 H33 M14 U23 HPND Yes Details →
9.0.1 03 Feb 2022 C4 H32 M12 U20 HPND Yes Details →
9.0.0 02 Jan 2022 C5 H33 M12 U21 HPND Yes Details →
8.4.0 15 Oct 2021 C5 H33 M14 L1 U24 HPND Yes Details →
8.3.2 02 Sep 2021 C5 H33 M14 L1 U24 HPND Yes Details →
8.3.1 06 Jul 2021 C5 H34 M14 L1 U25 HPND Yes Details →
8.3.0 01 Jul 2021 C5 H34 M14 L1 U25 HPND Yes Details →
8.2.0 01 Apr 2021 C6 H34 M14 L1 U26 HPND Yes Details →
8.1.2 06 Mar 2021 C6 H39 M14 L1 U31 HPND Yes Details →
8.1.1 02 Mar 2021 C6 H42 M15 L1 U31 HPND Yes Details →
8.1.0 02 Jan 2021 C7 H44 M16 L1 U39 HPND Yes Details →
8.0.1 22 Oct 2020 C7 H44 M17 L1 U42 HPND Yes Details →
8.0.0 14 Oct 2020 C7 H44 M17 L1 U42 HPND Yes Details →
7.2.0 30 Jun 2020 C7 H44 M17 L1 U42 HPND Yes Details →
7.1.2 25 Apr 2020 C7 H43 M17 L1 U42 HPND Yes Details →
7.1.1 02 Apr 2020 C7 H43 M17 L1 U42 HPND Yes Details →
7.1.0 01 Apr 2020 C7 H43 M17 L1 U42 HPND Yes Details →
7.0.0 02 Jan 2020 C8 H47 M17 L1 U46 HPND Yes Details →
6.2.2 02 Jan 2020 C8 H47 M17 L1 U47 HPND Yes Details →
6.2.1 21 Oct 2019 C12 H49 M17 L1 U53 HPND Yes Details →
6.2.0 01 Oct 2019 C12 H49 M17 L1 U53 HPND Yes Details →
6.1.0 03 Jul 2019 C12 H50 M17 L1 U55 HPND Yes Details →
6.0.0 02 Apr 2019 C12 H50 M17 L1 U55 HPND Yes Details →
5.4.1 06 Jan 2019 C12 H50 M17 L1 U55 non-standard Yes Details →
5.4.0 01 Jan 2019 C12 H50 M17 L1 U55 non-standard Yes Details →
5.3.0 01 Oct 2018 C12 H50 M16 L1 U55 non-standard Yes Details →
5.2.0 02 Jul 2018 C12 H49 M16 L1 U55 non-standard Yes Details →
5.1.0 02 Apr 2018 C12 H48 M15 L1 U54 non-standard Yes Details →
5.0.0 01 Jan 2018 C12 H43 M12 L1 U53 non-standard Yes Details →
4.3.0 02 Oct 2017 C12 H43 M12 L1 U53 non-standard Yes Details →
4.2.1 06 Jul 2017 C12 H42 M11 L1 U52 non-standard Yes Details →
4.2.0 01 Jul 2017 C12 H42 M11 L1 U52 non-standard Yes Details →
4.1.1 28 Apr 2017 C12 H42 M10 L1 U51 non-standard Yes Details →
4.1.0 04 Apr 2017 C12 H42 M10 L1 U51 non-standard Yes Details →
4.0.0 02 Jan 2017 C12 H41 M10 L1 U51 non-standard Yes Details →
3.4.2 18 Oct 2016 C12 H41 M10 L1 U51 non-standard Yes Details →
3.4.1 04 Oct 2016 C12 H41 M10 L1 U51 non-standard Yes Details →
3.3.3 04 Oct 2016 C12 H41 M10 L1 U51 non-standard Yes Details →
3.4.0 03 Oct 2016 C12 H41 M10 L1 U51 non-standard Yes Details →
3.3.2 03 Oct 2016 C12 H41 M10 L1 U51 non-standard Yes Details →
3.3.1 18 Aug 2016 C12 H42 M11 L1 U53 non-standard Yes Details →
3.3.0 01 Jul 2016 C12 H42 M11 L1 U53 non-standard Yes Details →
3.2.0 01 Apr 2016 C12 H42 M11 L1 U53 non-standard Yes Details →
3.1.2 01 Apr 2016 C12 H42 M11 L1 U53 non-standard Yes Details →
3.1.1 04 Feb 2016 C12 H43 M11 L1 U54 non-standard Yes Details →
3.1.0 04 Jan 2016 C13 H45 M12 L1 U58 non-standard Yes Details →
3.0.0 01 Oct 2015 C13 H45 M12 L1 U58 non-standard Yes Details →
2.9.0 01 Jul 2015 C13 H45 M12 L1 U58 non-standard Yes Details →
2.8.2 07 Jun 2015 C13 H45 M12 L1 U58 non-standard Yes Details →
2.8.1 02 Apr 2015 C13 H45 M12 L1 U58 non-standard Yes Details →
2.8.0 02 Apr 2015 C13 H45 M12 L1 U58 non-standard Yes Details →
2.7.0 01 Jan 2015 C13 H45 M12 L1 U58 non-standard Yes Details →
2.6.2 01 Jan 2015 C13 H46 M12 L1 U59 non-standard Yes Details →
2.6.1 13 Oct 2014 C13 H46 M12 L1 U59 non-standard Yes Details →
2.6.0 01 Oct 2014 C13 H46 M12 L1 U59 non-standard Yes Details →
2.5.3 18 Aug 2014 C12 H46 M12 L1 U59 non-standard Yes Details →
2.3.2 13 Aug 2014 C13 H44 M12 L1 U60 non-standard Yes Details →
2.5.2 13 Aug 2014 C12 H47 M12 L1 U60 non-standard Yes Details →
2.5.1 10 Jul 2014 C12 H47 M12 L1 U61 non-standard Yes Details →
2.5.0 01 Jul 2014 C12 H47 M12 L1 U61 non-standard Yes Details →
2.4.0 01 Apr 2014 C13 H46 M12 L1 U60 non-standard Yes Details →
2.3.1 15 Mar 2014 C13 H45 M12 L1 U61 non-standard Yes Details →
2.3.0 01 Jan 2014 C13 H46 M13 L1 U63 non-standard Yes Details →
2.2.2 16 Dec 2013 C13 H46 M12 L1 U63 non-standard Yes Details →
2.2.1 02 Oct 2013 C13 H46 M12 L1 U63 non-standard Yes Details →
2.2.0 02 Oct 2013 C13 H46 M12 L1 U63 non-standard Yes Details →
2.1.0 02 Jul 2013 C13 H46 M12 L1 U63 non-standard Yes Details →
2.0.0 15 Mar 2013 C13 H46 M12 L1 U63 non-standard Yes Details →
1.7.8 01 Nov 2012 C12 H46 M12 L1 U63 — Yes Details →
1.7.7 05 Apr 2012 C12 H46 M12 L1 U63 — Yes Details →
1.7.6 21 Jan 2012 C12 H46 M12 L1 U63 — Yes Details →
1.7.5 07 Sep 2011 C12 H46 M12 L1 U63 — Yes Details →
1.7.4 21 Jul 2011 C12 H46 M12 L1 U63 — Yes Details →
1.7.3 21 Jul 2011 C12 H46 M12 L1 U63 — Yes Details →
1.7.2 02 Jun 2011 C12 H46 M12 L1 U63 — Yes Details →
1.7.1 31 May 2011 C12 H46 M12 L1 U63 — Yes Details →
1.7.0 28 May 2011 C12 H46 M12 L1 U63 — Yes Details →
1.6.0 01 Dec 2010 C12 H46 M12 L1 U63 — Yes Details →
1.5.0 28 Nov 2010 C12 H46 M12 L1 U63 — Yes Details →
1.4.0 28 Nov 2010 C12 H46 M12 L1 U63 — Yes Details →
1.3.0 28 Nov 2010 C12 H46 M12 L1 U63 — Yes Details →
1.2.0 02 Aug 2010 C12 H46 M12 L1 U63 — Yes Details →
1.1.0 01 Aug 2010 C12 H46 M12 L1 U63 — Yes Details →
1.0.0 31 Jul 2010 C12 H46 M12 L1 U63 — Yes Details →
1.7.5-py2.4-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.5-py2.5-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.5-py2.6-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.5-py2.7-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.6-py2.4-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.6-py2.5-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.6-py2.6-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.6-py2.7-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.7-py2.4-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.7-py2.5-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.7-py2.6-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.7-py2.7-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.8-py2.4-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.8-py2.5-win32 — C12 H46 M12 L1 U63 — Yes Details →
1.7.8-py2.6-win-amd64 — C12 H46 M12 L1 U63 — Yes Details →

The newest 120 of 947 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 4
  • 2015 2
  • 2016 6
  • 2017 1
  • 2018 6
  • 2019 3
  • 2020 18
  • 2021 42
  • 2022 25
  • 2023 4
  • 2024 3
  • 2025 2
  • 2026 80

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 80 of the 196 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for pillow

The 5 most severe of 196 vulnerabilities recorded for this package

Search all 196 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About pillow

Is pillow safe to use?

Vulert records 196 vulnerabilities for pillow in PyPI: 15 critical, 74 high, 27 medium and 1 low, plus 79 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is pillow's Vulert package health score?

Vulert scores pillow 66/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of pillow affected?

Yes. 13.0.0, the version you would install today, has 8 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of pillow should I use?

13.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does pillow have?

196 vulnerabilities are recorded for pillow in the PyPI ecosystem: 15 critical, 74 high, 27 medium and 1 low, plus 79 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pillow vulnerabilities disclosed?

80 vulnerabilities were recorded for pillow in the last 12 months, and the oldest entry in this database dates to 17 Apr 2014. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of pillow are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor pillow for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pillow version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.