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

CVE-2026-46603 · Severity: info · Published 2026-08-14

Excessive memory allocation during VP8L decoding in golang.org/x/image

Technologies: golang.org/x/image (Go). Vendors: Go.

Quick answers

Is CVE-2026-46603 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-46603 being exploited in the wild.
How severe is CVE-2026-46603?
Informational severity, published 14 August 2026.
Which products and versions are affected?
golang.org/x/image (Go) SEMVER:introduced=0,fixed=0.45.0.
Is there a fix for CVE-2026-46603?
Yes. golang.org/x/image (Go): upgrade to 0.45.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-46603?
Check whether you run golang.org/x/image (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • golang.org/x/image (Go): upgrade to 0.45.0 or later
    go get golang.org/x/image@v0.45.0

Affected products

  • golang.org/x/image (Go) SEMVER:introduced=0,fixed=0.45.0

Identifiers

  • CVE-2026-46603
  • GO-2026-6222

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.