CVE-2026-46603

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

August 14, 2026

Last Modified

September 3, 2026

Advisory Details (3)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

GO-2026-6222 - Go Packages

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

x/image/vp8l: excessive memory allocation from unused Huffman tree groups · Issue #80069 · golang/go · GitHub

https://go.dev/issue/80069

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-image0.11.0-1 ... 0.9.0-1 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-image0.18.0-1 ... 0.45.0-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-image0.18.0-1 ... 0.42.0-1 (6 versions)0.45.0-1—
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/image—0.45.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 03:03 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 01:49 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 23:49 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 13:04 UTCEG score recompute
  9. 2026-09-13 22:30 UTCEG score recompute
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-12 21:26 UTCEG score recompute
  12. 2026-09-12 15:01 UTCEPSS rescore
  13. 2026-09-11 20:21 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 09:37 UTCEPSS rescore
  16. 2026-09-10 18:45 UTCEG score recompute
  17. 2026-09-10 09:34 UTCEPSS rescore
  18. 2026-09-09 04:49 UTCEG score recompute
  19. 2026-09-08 22:00 UTCEPSS rescore
  20. 2026-09-07 16:25 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 21:28 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-05 20:19 UTCEG score recompute
  25. 2026-09-04 19:13 UTCEG score recompute
Show 41 more
  1. 2026-09-04 06:12 UTCEG score recompute
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-03 00:57 UTCEG score recompute
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 23:45 UTCEG score recompute
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 11:13 UTCEG score recompute
  8. 2026-08-30 21:30 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 08:58 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 06:55 UTCEG score recompute
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 21:57 UTCEG score recompute
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 20:52 UTCEG score recompute
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 19:46 UTCEG score recompute
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 18:41 UTCEG score recompute
  21. 2026-08-23 05:02 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 03:56 UTCEG score recompute
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-21 02:51 UTCEG score recompute
  26. 2026-08-20 22:55 UTCEPSS rescore
  27. 2026-08-20 01:45 UTCEG score recompute
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-19 00:40 UTCEG score recompute
  30. 2026-08-18 13:48 UTCEPSS rescore
  31. 2026-08-17 23:31 UTCEG score recompute
  32. 2026-08-17 13:47 UTCEPSS rescore
  33. 2026-08-16 22:27 UTCEG score recompute
  34. 2026-08-16 14:56 UTCEPSS rescore
  35. 2026-08-16 09:55 UTCEG score recompute
  36. 2026-08-16 02:14 UTCEPSS rescore
  37. 2026-08-14 19:54 UTCEG score recompute▲ 7.50
  38. 2026-08-14 19:53 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  39. 2026-08-14 17:33 UTCNVD update
  40. 2026-08-14 16:44 UTCEG score recompute
  41. 2026-08-14 16:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46603?
CVE-2026-46603 is a high vulnerability published on August 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.
When was CVE-2026-46603 disclosed?
CVE-2026-46603 was first published in the National Vulnerability Database on August 14, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46603 actively exploited?
CVE-2026-46603 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.3% of all scored CVEs.
What is the CVSS score of CVE-2026-46603?
CVE-2026-46603 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-46603?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46603, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46603

Explore →

Is Your Infrastructure Affected by CVE-2026-46603?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs