Live › vulnerability › CVE-2026-112891
Go to dashboardPillow's GIF saver copies portions of a long comment repeatedly, so saving a crafted GIF takes quadratic CPU time. An attacker who can get a service to re-save an uploaded GIF can tie up CPU, causing denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| pillow | pypi | >= 9.2.0, < 13.0.0 | 13.0.0 |
pip show pillow (affected if version >= 9.2.0 and < 13.0.0)
Check whether the app saves uploaded GIFs with Pillow (Image.save with format GIF) and whether it preserves comments from input images
13.0.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
On Pillow 12.3.0 and upstream main (ad277e2761b489681e71b51e91367d46b0ceabb9), a GIF with a long comment makes _get_global_header() copy portions of the comment repeatedly when saving, including comments carried over from untrusted images. I suggest provisional Moderate severity for crafted-image CPU denial of service, with CVSS-B 6.9 assuming a network service automatically opens unauthenticated uploads and they are resaved as GIFs; impact depends on input-size, concurrency, and worker CPU limits.
This page as .md · .json · in your agent: get_signal("CVE-2026-112891")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.