Answer in brief
CVE-2026-46603 records a Unknown severity vulnerability in Excessive memory allocation during VP8L decoding in golang.org/x/image. The current sources do not mark it as known exploited. The current feed maps golang.org/x/image/golang.org/x/image/vp8l (generic), golang.org/x/image (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps golang.org/x/image/golang.org/x/image/vp8l (generic), golang.org/x/image (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| golang.org/x/image/golang.org/x/image/vp8lgeneric | >=0 <0.45.0 | 0.45.0 |
| golang.org/x/imagego | >=0 <0.45.0 | 0.45.0 |
Published upstream
Aug 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-46603 records a Unknown severity vulnerability in Excessive memory allocation during VP8L decoding in golang.org/x/image. The current sources do not mark it as known exploited. The current feed maps golang.org/x/image/golang.org/x/image/vp8l (generic), golang.org/x/image (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps golang.org/x/image/golang.org/x/image/vp8l (generic), golang.org/x/image (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| golang.org/x/image/golang.org/x/image/vp8lgeneric | >=0 <0.45.0 | 0.45.0 |
| golang.org/x/imagego | >=0 <0.45.0 | 0.45.0 |
Published upstream
Aug 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.