CVE-2026-33813

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.3%, top 73% 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

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)
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
28%
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
generic
https://go.dev/cl/759860

Vendor Advisories for CVE-2026-33813(9)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift-logging/cluster-logging-rhel9-operator:17824128152026-07-01redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17799252732026-06-08redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17801671182026-06-04redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17795794392026-06-01redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17788677532026-05-28redhat
redhatcryostat/cryostat-storage-rhel9:4.2.0-132026-05-26redhat
redhatgolang1-26-main-1.26.2-1.1.hum12026-04-15redhat
redhatgolang1-25-main-1.25.9-1.hum12026-04-10redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-image0.0~git20200119.58c2397-1 ... 0.9.0-1 (22 versions)——
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.32.0-1, 0.35.0-1, 0.38.0-10.39.0-1—
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/image—0.42.0—

Data Freshness Timeline

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

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:11 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-02 03:09 UTCOSV refresh
  18. 2026-09-01 13:53 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-08-30 19:17 UTCEPSS rescore
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-28 21:41 UTCEPSS rescore
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-26 14:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 14:17 UTCEPSS rescore
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 06:17 UTCEG score recompute
  12. 2026-08-16 06:17 UTCVendor advisory
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 15:42 UTCVendor advisory
  16. 2026-08-14 04:28 UTCEG score recompute
  17. 2026-08-14 04:28 UTCVendor advisory
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 08:43 UTCVendor advisory
  20. 2026-08-12 18:39 UTCEG score recompute
  21. 2026-08-12 18:39 UTCVendor advisory
  22. 2026-08-12 13:50 UTCEPSS rescore
  23. 2026-08-11 16:51 UTCEG score recompute
  24. 2026-08-11 16:51 UTCVendor advisory
  25. 2026-08-11 02:25 UTCEG score recompute
  26. 2026-08-11 02:25 UTCVendor advisory
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-10 02:09 UTCVendor advisory
  29. 2026-08-09 14:55 UTCEG score recompute
  30. 2026-08-09 14:55 UTCVendor advisory
  31. 2026-08-09 13:46 UTCEPSS rescore
  32. 2026-08-09 03:40 UTCEG score recompute
  33. 2026-08-09 03:40 UTCVendor advisory
  34. 2026-08-08 16:37 UTCEPSS rescore
  35. 2026-08-08 11:25 UTCVendor advisory
  36. 2026-08-08 00:11 UTCEG score recompute
  37. 2026-08-08 00:11 UTCVendor advisory
  38. 2026-08-07 12:56 UTCVendor advisory
  39. 2026-08-06 21:49 UTCEG score recompute
  40. 2026-08-06 21:49 UTCVendor advisory
  41. 2026-08-06 13:46 UTCEPSS rescore
  42. 2026-08-06 10:25 UTCVendor advisory
  43. 2026-08-05 23:10 UTCEG score recompute
  44. 2026-08-05 23:10 UTCVendor advisory
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-04 15:10 UTCEPSS rescore
  47. 2026-08-04 10:38 UTCEPSS rescore
  48. 2026-08-03 21:22 UTCEG score recompute
  49. 2026-08-03 21:22 UTCVendor advisory
  50. 2026-08-03 10:36 UTCEPSS rescore
  51. 2026-08-02 23:59 UTCVendor advisory
  52. 2026-08-02 12:44 UTCEG score recompute
  53. 2026-08-02 12:44 UTCVendor advisory
  54. 2026-08-02 02:27 UTCEPSS rescore
  55. 2026-08-01 04:16 UTCEPSS rescore
  56. 2026-07-30 16:28 UTCEPSS rescore
  57. 2026-07-30 01:30 UTCEPSS rescore
  58. 2026-07-27 14:13 UTCEPSS rescore
  59. 2026-07-26 14:54 UTCEPSS rescore
  60. 2026-07-26 14:54 UTCEPSS rescore
  61. 2026-07-25 14:18 UTCEPSS rescore
  62. 2026-07-25 14:18 UTCEPSS rescore
  63. 2026-07-24 14:17 UTCEPSS rescore
  64. 2026-07-24 14:17 UTCEPSS rescore
  65. 2026-07-23 14:18 UTCEPSS rescore
  66. 2026-07-23 14:18 UTCEPSS rescore
  67. 2026-07-23 03:09 UTCEG score recompute
  68. 2026-07-22 14:08 UTCEPSS rescore
  69. 2026-07-20 20:32 UTCOSV refresh
  70. 2026-07-20 17:08 UTCEPSS rescore
  71. 2026-07-19 14:31 UTCEPSS rescore
  72. 2026-07-19 02:29 UTCEPSS rescore
  73. 2026-07-18 10:04 UTCEPSS rescore
  74. 2026-07-16 17:03 UTCEPSS rescore
  75. 2026-07-15 16:57 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 0% probability of exploitation in the next 30 days, which ranks it in the top 72.4% of all scored CVEs.
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.

Start Free Scan →Browse All CVEs