VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.
Product
golang.org/x/image vulnerabilities
13 published CVES affecting golang.org/x/image, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 13
- Critical
- 0
- High
- 7
- Medium
- 6
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest golang.org/x/image CVEs
Newest publication first
-
HighCVSS 7.5 EPSS 0.41%
-
HighCVSS 7.5 EPSS 0.61%
The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.
-
HighCVSS 7.5 EPSS 0.61%
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-46601 Panic on VP8 alpha channel size mismatch in x/image/webp in golang.org/x/image
PublishedHighCVSS 7.5 EPSS 0.61%The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.
-
CVE-2026-46599 Excessive resource consumption in PackBits decompression in golang.org/x/image/tiff
PublishedHighCVSS 7.5 EPSS 0.35%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.
-
MediumCVSS 5.3 EPSS 0.38%
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-33812 Excessive memory allocation when decoding malicious SFNT in golang.org/x/image
PublishedMediumCVSS 6.1 EPSS 0.12%Parsing a malicious font file can cause excessive memory allocation.
-
CVE-2026-33813 Panic when decoding large WEBP image on 32-bit platforms in golang.org/x/image
PublishedHighCVSS 7.5 EPSS 0.35%Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.
-
MediumCVSS 5.3 EPSS 0.34%
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.
-
HighCVSS 7.5 EPSS 0.73%
Parsing a corrupt or malicious image with invalid color indices can cause a panic.
-
CVE-2023-29407 Excessive CPU consumption when decoding 0-height images in golang.org/x/image/tiff
PublishedMediumCVSS 6.5 EPSS 0.87%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.
-
MediumCVSS 6.5 EPSS 0.93%
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...
-
MediumCVSS 5.5 EPSS 0.31%
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.