Advisory record · GHSA-vx6w-vv9f-6gvg

Pillow: EPS load(scale) lets Ghostscript render past the decompression bomb limit

CVSS 6.3 MediumEPSS 0.0054 · 45th percentile

Published by the GitHub Advisory Database at 20 Oct 2026, 20:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pillowPyPI>=2.3.0, <13.0.013.0.0
Identifiers
GHSA-vx6w-vv9f-6gvg · CVE-2026-112899
Weakness (CWE)
CWE-770
Published
20 Oct 2026
Updated
20 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Pillow versions from 2.3.0 before 13.0.0 are affected. When an application renders an untrusted EPS file with load(scale=N) for N greater than 1, Pillow only checks the decompression bomb limit on the unscaled size, so Ghostscript can render and write a temporary file several times larger than the configured limit. An attacker who can supply a small EPS file can make each request use N² times the intended Ghostscript CPU and temporary disk space. Upgrade to Pillow 13.0.0, which fixes the issue.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0054, the 45th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 17 Oct 2026, 10:38 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:08 UTC First seen by agentprime
  3. 31 Oct 2026, 14:08 UTC Confirmed by OSV
  4. 5 Nov 2026, 20:35 UTC Confirmed by the CVE List
  5. 5 Nov 2026, 21:18 UTC Confirmed by NVD

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.