There are 8 open security issues in trixie.
8 issues left for the package maintainer to handle:
- CVE-2026-33809:
(needs triaging)
A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.
- CVE-2026-33812:
(needs triaging)
Parsing a malicious font file can cause excessive memory allocation.
- CVE-2026-33813:
(needs triaging)
Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.
- CVE-2026-42500:
(needs triaging)
Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.
- CVE-2026-46599:
(needs triaging)
The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.
- CVE-2026-46601:
(needs triaging)
The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.
- CVE-2026-46602:
(needs triaging)
The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.
- CVE-2026-46604:
(needs triaging)
The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.
You can find information about how to handle these issues in the security team's documentation.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/g/golang-golang-x-image.png){kind=link}