Vulnerabilities

Security fix · CVE-2026-112899

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

Published Oct 20, 2026 · catalog updated Oct 20, 2026 · Pillow: EPS load(scale) lets

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-112899. A missing EPSS score is not a low risk. Compare Pillow: EPS load(scale) lets with the linked advisory before you change production.

Severity

Medium—

Known exploitation

Not in CISA/VulnCheck KEV

EPSS

Not in the current FIRST EPSS dataset

Remediation

Version ranges on file

Affected products

package pip · pip Pillow

When an application opens an untrusted Encapsulated PostScript file and asks Pillow to render it at a larger scale, Pillow has Ghostscript produce an image several times bigger than Pillow's configured size limit allows. The size check runs only after Ghostscript has finished rendering and written the full raw image to a temporary file. An attacker who can upload a file of about 100 bytes makes each such request spend scale² times the Ghostscript rendering work and temporary disk space that the limit is meant to permit. For example, at scale 2 that is a 972 MB temporary file. The cause is in in . It multiplies the file-declared size by the caller's (lines 93-94) and passes the product to as the output geometry. It never calls on the scaled size. The only check is the one ran on the unscaled size, so a file declaring 9000×9000 passes, and then asks Ghostscript for 18000×18000 (3.6× ). A file declaring 18000×18000 directly would be refused before Ghostscript ever ran. fires only when Pillow reopens the output file, so Pillow's own in-process allocation stays bounded and there is no memory corruption. The effect is a constant-factor overshoot rather than an unbounded one, for three reasons: * The multiplier is an integer chosen by the application, not by the file. * With the default warning filter, already lets files up to 2× the limit reach Ghostscript at . * Any application feeding untrusted files to Ghostscript is already exposed to a tiny file that keeps Ghostscript busy indefinitely, since runs with no timeout. This is the EPS counterpart of the WMF gap closed in af70b075a. It has been present since the decompression-bomb limit was introduced in ce2955ec7 (2.5.0). The attached reproducer stubs out Ghostscript and shows a 76-byte file passing and reaching with . A one-line patch mirroring the WMF check is included. ## Details (the documented way to rasterise an EPS at higher resolution) renders pixels through Ghostscript, but the only decompression-bomb check on th