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% (33rd percentile of EPSS-scored CVEs). 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
Trending — 3 sources updated this week
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.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 14, 2026

Last Modified

September 3, 2026

Advisory Details (3)

Auto-updated Aug 14, 2026
Patch available.
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

Vendor Advisories for CVE-2026-46603(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhacm2/volsync-rhel9:17901034292026-09-23redhat
redhatrhacm2/volsync-rhel9:17901034682026-09-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-image0.11.0-1 ... 0.9.0-1 (17 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-image0.18.0-1 ... 0.45.0-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-image0.18.0-1 ... 0.42.0-1 (6 versions)
  • every version up to 0.45.0-1: fixed in 0.45.0-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
golang.org/x/image—
  • every version up to 0.45.0: fixed in 0.45.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 63× 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.

Showing the most recent 100 of 112 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 22:54 UTCEG score recompute
  5. 2026-10-06 22:54 UTCVendor advisory
  6. 2026-10-06 15:18 UTCEPSS rescore
  7. 2026-10-06 09:22 UTCEG score recompute
  8. 2026-10-06 09:22 UTCVendor advisory
  9. 2026-10-05 17:43 UTCEPSS rescore
  10. 2026-10-05 13:02 UTCEG score recompute
  11. 2026-10-05 13:02 UTCVendor advisory
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-04 22:12 UTCVendor advisory
  14. 2026-10-04 08:14 UTCVendor advisory
  15. 2026-10-03 19:41 UTCEG score recompute
  16. 2026-10-03 19:41 UTCVendor advisory
  17. 2026-10-03 14:25 UTCEPSS rescore
  18. 2026-10-02 19:53 UTCEG score recompute
  19. 2026-10-02 19:53 UTCVendor advisory
  20. 2026-10-02 07:21 UTCEG score recompute
  21. 2026-10-02 07:21 UTCVendor advisory
  22. 2026-10-01 19:50 UTCEPSS rescore
  23. 2026-10-01 10:12 UTCVendor advisory
  24. 2026-09-30 21:40 UTCEG score recompute
  25. 2026-09-30 21:40 UTCVendor advisory
Show 75 more
  1. 2026-09-30 15:03 UTCEPSS rescore
  2. 2026-09-29 02:55 UTCEG score recompute
  3. 2026-09-29 02:55 UTCVendor advisory
  4. 2026-09-28 13:51 UTCEPSS rescore
  5. 2026-09-28 12:08 UTCVendor advisory
  6. 2026-09-27 23:32 UTCEG score recompute
  7. 2026-09-27 23:32 UTCVendor advisory
  8. 2026-09-27 13:48 UTCEPSS rescore
  9. 2026-09-27 09:37 UTCEG score recompute
  10. 2026-09-27 09:37 UTCVendor advisory
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-26 00:27 UTCEPSS rescore
  13. 2026-09-25 03:23 UTCEG score recompute
  14. 2026-09-25 03:23 UTCVendor advisory
  15. 2026-09-23 22:00 UTCEG score recompute
  16. 2026-09-23 17:53 UTCEPSS rescore
  17. 2026-09-22 20:56 UTCEG score recompute
  18. 2026-09-22 08:17 UTCEG score recompute
  19. 2026-09-21 06:14 UTCEG score recompute
  20. 2026-09-20 20:15 UTCEPSS rescore
  21. 2026-09-19 16:15 UTCEG score recompute
  22. 2026-09-19 03:03 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-18 01:49 UTCEG score recompute
  25. 2026-09-17 19:31 UTCEPSS rescore
  26. 2026-09-16 23:49 UTCEG score recompute
  27. 2026-09-16 14:08 UTCEPSS rescore
  28. 2026-09-16 05:15 UTCEPSS rescore
  29. 2026-09-15 13:04 UTCEG score recompute
  30. 2026-09-13 22:30 UTCEG score recompute
  31. 2026-09-13 16:47 UTCEPSS rescore
  32. 2026-09-12 21:26 UTCEG score recompute
  33. 2026-09-12 15:01 UTCEPSS rescore
  34. 2026-09-11 20:21 UTCEG score recompute
  35. 2026-09-11 14:53 UTCEPSS rescore
  36. 2026-09-11 09:37 UTCEPSS rescore
  37. 2026-09-10 18:45 UTCEG score recompute
  38. 2026-09-10 09:34 UTCEPSS rescore
  39. 2026-09-09 04:49 UTCEG score recompute
  40. 2026-09-08 22:00 UTCEPSS rescore
  41. 2026-09-07 16:25 UTCEG score recompute
  42. 2026-09-07 16:01 UTCEPSS rescore
  43. 2026-09-06 21:28 UTCEG score recompute
  44. 2026-09-06 13:47 UTCEPSS rescore
  45. 2026-09-05 20:19 UTCEG score recompute
  46. 2026-09-04 19:13 UTCEG score recompute
  47. 2026-09-04 06:12 UTCEG score recompute
  48. 2026-09-04 05:06 UTCEPSS rescore
  49. 2026-09-03 00:57 UTCEG score recompute
  50. 2026-09-02 14:12 UTCEPSS rescore
  51. 2026-09-01 23:45 UTCEG score recompute
  52. 2026-09-01 13:54 UTCEPSS rescore
  53. 2026-09-01 11:13 UTCEG score recompute
  54. 2026-08-30 21:30 UTCEG score recompute
  55. 2026-08-30 19:17 UTCEPSS rescore
  56. 2026-08-30 08:58 UTCEG score recompute
  57. 2026-08-30 01:22 UTCEPSS rescore
  58. 2026-08-29 06:55 UTCEG score recompute
  59. 2026-08-28 21:41 UTCEPSS rescore
  60. 2026-08-27 21:57 UTCEG score recompute
  61. 2026-08-27 14:25 UTCEPSS rescore
  62. 2026-08-26 20:52 UTCEG score recompute
  63. 2026-08-26 14:46 UTCEPSS rescore
  64. 2026-08-25 19:46 UTCEG score recompute
  65. 2026-08-25 13:49 UTCEPSS rescore
  66. 2026-08-24 18:41 UTCEG score recompute
  67. 2026-08-23 05:02 UTCEG score recompute
  68. 2026-08-23 00:19 UTCEPSS rescore
  69. 2026-08-22 03:56 UTCEG score recompute
  70. 2026-08-21 23:49 UTCEPSS rescore
  71. 2026-08-21 02:51 UTCEG score recompute
  72. 2026-08-20 22:55 UTCEPSS rescore
  73. 2026-08-20 01:45 UTCEG score recompute
  74. 2026-08-19 17:04 UTCEPSS rescore
  75. 2026-08-19 00:40 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2026:71116

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 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.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-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?
A fix for CVE-2026-46603 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46603 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs