Source: pillow
Version: 12.2.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: [email protected], Debian Security Team <[email protected]>
Hi,
The following vulnerabilities were published for pillow.
For unstable it is probably just best to move to 12.3.0 rather than
picking individual fixes so we get the version included in forky.
CVE-2026-54058[0]:
| Pillow is a Python imaging library. Prior to 12.3.0, when Pillow
| loads an uncompressed McIdas AREA image from a filename through the
| mmap raw codec path, attacker-controlled header words can set a row
| stride smaller than the natural row width, causing pixel access such
| as Image.tobytes(), getpixel, convert, or save to read beyond the
| mapped region and disclose adjacent process memory or fault. This
| issue is fixed in version 12.3.0.
CVE-2026-54059[1]:
| Pillow is a Python imaging library. Prior to 12.3.0,
| PIL/PcfFontFile.py _load_bitmaps() read glyph dimensions from the
| PCF METRICS section and passed them directly to Image.frombytes()
| without calling Image._decompression_bomb_check(), allowing crafted
| PCF font data to cause excessive memory allocation. This issue is
| fixed in version 12.3.0.
CVE-2026-54060[2]:
| Pillow is a Python imaging library. Prior to 12.3.0, PIL/FontFile.py
| FontFile.compile() assembled per-glyph images into a combined bitmap
| with Image.new("1", (xsize, ysize)) without calling
| Image._decompression_bomb_check(), allowing a font to trigger
| excessive allocation during conversion or saving. This issue is
| fixed in version 12.3.0.
CVE-2026-55379[3]:
| Pillow is a Python imaging library. Prior to 12.3.0,
| PIL/BdfFontFile.py bdf_char() read the BBX width and height field
| from a BDF font file and passed attacker-controlled dimensions to
| Image.new() without calling Image._decompression_bomb_check(),
| bypassing Pillow's documented decompression bomb protection and
| allowing excessive memory allocation. This issue is fixed in version
| 12.3.0.
CVE-2026-55380[4]:
| Pillow is a Python imaging library. Prior to 12.3.0,
| PIL/GdImageFile.py GdImageFile._open() read image dimensions from
| the GD 2.x header and stored them in self._size without calling
| Image._decompression_bomb_check(), allowing a crafted .gd file to
| trigger excessive C-heap allocation when loaded. This issue is fixed
| in version 12.3.0.
CVE-2026-59197[5]:
| Pillow is a Python imaging library. Prior to 12.3.0, Pillow's public
| rank-filter API can trigger a native heap out-of-bounds write when
| given a very large odd filter size because
| ImageFilter.RankFilter.filter() calls image.expand(size // 2, size
| // 2) before rank-filter size validation and ImagingExpand()
| computes output dimensions with unchecked signed int arithmetic.
| This issue is fixed in version 12.3.0.
CVE-2026-59198[6]:
| Pillow is a Python imaging library. From 5.2.0 until 12.3.0,
| Pillow's TGA RLE encoder reads past its packed row buffer when
| saving a mode 1 image with TGA RLE compression, allowing adjacent
| process heap bytes to be copied into the generated TGA file. This
| issue is fixed in version 12.3.0.
CVE-2026-59199[7]:
| Pillow is a Python imaging library. Prior to 12.3.0, Pillow public
| image coordinate APIs can trigger a native heap out-of-bounds write
| when given coordinates near the signed 32-bit integer limits in
| Image.paste(), Image.crop(), or Image.alpha_composite(). This issue
| is fixed in version 12.3.0.
CVE-2026-59200[8]:
| Pillow is a Python imaging library. From 5.1.0 until 12.3.0,
| PdfParser.PdfStream.decode() in PIL/PdfParser.py calls
| zlib.decompress() with bufsize set to the PDF stream Length field
| without bounding the decompressed output size, allowing a crafted
| FlateDecode PDF stream to exhaust memory from a small file. This
| issue is fixed in version 12.3.0.
CVE-2026-59203[9]:
| Pillow is a Python imaging library. From 12.0.0 through 12.2.0,
| Pillow's EPS parser in PIL/EpsImagePlugin.py accepts a negative byte
| count in the %%BeginBinary directive, allowing a crafted EPS file to
| cause Image.open() to seek backwards to the same directive and parse
| it repeatedly in an infinite loop. This issue is fixed in version
| 12.3.0.
CVE-2026-59204[10]:
| Pillow is a Python imaging library. From 8.2.0 through 12.2.0,
| src/libImaging/Jpeg2KDecode.c accumulates total_component_width
| across every tile in a JPEG2000 image instead of recomputing it per
| tile, allowing a crafted tiled JPEG2000 file to force substantially
| higher transient memory usage and trigger out-of-memory failures
| during decoding. This issue is fixed in version 12.3.0.
CVE-2026-59205[11]:
| Pillow is a Python imaging library. Prior to 12.3.0, Pillow's
| ImageCms.ImageCmsTransform.apply(im, imOut) API can trigger
| controlled native heap corruption when the caller supplies an output
| image whose mode does not match the transform's declared output
| mode. This issue is fixed in version 12.3.0.
If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2026-54058
https://www.cve.org/CVERecord?id=CVE-2026-54058
[1] https://security-tracker.debian.org/tracker/CVE-2026-54059
https://www.cve.org/CVERecord?id=CVE-2026-54059
[2] https://security-tracker.debian.org/tracker/CVE-2026-54060
https://www.cve.org/CVERecord?id=CVE-2026-54060
[3] https://security-tracker.debian.org/tracker/CVE-2026-55379
https://www.cve.org/CVERecord?id=CVE-2026-55379
[4] https://security-tracker.debian.org/tracker/CVE-2026-55380
https://www.cve.org/CVERecord?id=CVE-2026-55380
[5] https://security-tracker.debian.org/tracker/CVE-2026-59197
https://www.cve.org/CVERecord?id=CVE-2026-59197
[6] https://security-tracker.debian.org/tracker/CVE-2026-59198
https://www.cve.org/CVERecord?id=CVE-2026-59198
[7] https://security-tracker.debian.org/tracker/CVE-2026-59199
https://www.cve.org/CVERecord?id=CVE-2026-59199
[8] https://security-tracker.debian.org/tracker/CVE-2026-59200
https://www.cve.org/CVERecord?id=CVE-2026-59200
[9] https://security-tracker.debian.org/tracker/CVE-2026-59203
https://www.cve.org/CVERecord?id=CVE-2026-59203
[10] https://security-tracker.debian.org/tracker/CVE-2026-59204
https://www.cve.org/CVERecord?id=CVE-2026-59204
[11] https://security-tracker.debian.org/tracker/CVE-2026-59205
https://www.cve.org/CVERecord?id=CVE-2026-59205
Regards,
Salvatore
