CVE-2026-46603: golang.org/x/image/vp8l · Excessive Memory Allocation
Affects golang.org/x/image/vp8lSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 0.45.0 soon.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.45.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade golang.org/x/image/vp8l to 0.45.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| golang.org/x/imagegolang.org/x/image/vp8l | Affected
| Fixed in
|
Gogolang.org/x/image/vp8lpkg:golang/golang.org/x/image/vp8lOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, avoid processing untrusted VP8L images or implement resource limits on memory usage during image decoding to mitigate potential denial of service.
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.