CVE-2026-33812 Excessive memory allocation when decoding malicious SFNT in golang.org/x/image
PublishedParsing a malicious font file can cause excessive memory allocation.
Product
6 published CVES affecting golang image, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
Newest publication first
Parsing a malicious font file can cause excessive memory allocation.
Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.
Parsing a corrupt or malicious image with invalid color indices can cause a panic.
A maliciously-crafted image can cause excessive CPU consumption in decoding. A tiled image with a height of 0 and a very large width can cause excessive CPU consumption, despite the image size (width * height) appearing to be zero.
The TIFF decoder does not place a limit on the size of compressed tile 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, consuming excessiv...
An attacker can craft a malformed TIFF image which will consume a significant amount of memory when passed to DecodeConfig. This could lead to a denial of service.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.