CVE-2026-33813

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 79% 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: epss, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
26.1%
KEV
Not listed

Published

April 21, 2026

Last Modified

June 25, 2026

Advisory Details (3)

Auto-updated Jun 7, 2026
No patch confirmed yet.
generic

GO-2026-4961 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4961
generic

x/image/webp: lack of maximum size checks can create invalid images on 32-bit platforms · Issue #78407 · golang/go · GitHub

https://go.dev/issue/78407

Patch Availability(7)

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/image0.39.0

Data Freshness Timeline

(refreshed 8× in last 7d / 46× 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 125 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-33813?
CVE-2026-33813 is a high vulnerability published on April 21, 2026. Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.
When was CVE-2026-33813 disclosed?
CVE-2026-33813 was first published in the National Vulnerability Database on April 21, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33813 actively exploited?
CVE-2026-33813 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33813?
CVE-2026-33813 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-33813?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33813, 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-33813

Explore →

Is Your Infrastructure Affected by CVE-2026-33813?

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