VDB

CVE-2026-46603

CVE-2026-46603 PUBLISHED CVSS 7.5 HIGH

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

Reported by go · Published August 14, 2026

golang.org/x/image/vp8l is fixed in 0.45.0 (Go Modules)

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
golang.org/x/image/vp8lGo Modules0.45.0
gitea-fipsChainguard1.27.2-r1
mattermost-11.7Wolfi11.7.9-r2
mattermost-11.7Chainguard11.7.9-r2
mattermost-fips-11.8Chainguard11.8.5-r2
seaweedfs-rocksdbChainguard4.40-r3
seaweedfs-operator-fipsChainguard1.0.34-r2
rclone-fipsChainguard1.75.0-r2
mattermost-11.6Wolfi11.6.6-r9, 11.6.6-r15
mattermost-11.4Chainguard11.4.5-r10
ollamaWolfi0.32.14-r1
seaweedfsChainguard4.41-r2

40 more packages have a fixed version. See every fix in Lookup.

Risk scores

CVSS 3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

VendorProductVersions
golang.org/x/imagegolang.org/x/image/vp8l0
wolfitailscale*
chainguardgitea-fips0
wolfimattermost-11.70
golang.org/x/imagegolang.org/x/image/vp8l0
chainguardgitlab-workhorse-ce-18.7*
wolfiglab*
chainguardmattermost-11.70
chainguardmattermost-fips-11.80
chainguardgitlab-workhorse-ce-fips-18.9*
chainguardseaweedfs-rocksdb0
chainguardseaweedfs-operator-fips0
chainguardgitlab-workhorse-ce-fips-19.0*
chainguardrclone-fips0
wolfimattermost-11.60, 0
chainguardgitlab-workhorse-ce-19.5*
chainguardmattermost-11.40
chainguardtailscale*
chainguardgitlab-workhorse-ce-fips-18.7*
wolfiollama0

…and 81 more

Timeline

  • Aug 14, 2026 CVE Published
  • Aug 15, 2026 Coalition ESS Score
  • Aug 24, 2026 EPSS Score (30 in total, the first dated here)
  • Sep 3, 2026 CVE Updated
  • Sep 6, 2026 Security Advisory

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-46603
vulnetix vdb fixes CVE-2026-46603

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-46603/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›