CVE-2026-33814

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 57% 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: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.

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

Published

May 7, 2026

Last Modified

July 6, 2026

Advisory Details (5)

Auto-updated May 8, 2026
No patch confirmed yet.
generic

GO-2026-4918 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4918
generic
https://groups.google.com/g/golang-announce/c/qcCIEXso47M
generic

net/http/internal/http2: SETTINGS_MAX_FRAME_SIZE=0 causes Transport to loop infinitely · Issue #78476 · golang/go · GitHub

https://go.dev/issue/78476
generic
https://go.dev/cl/761640
generic
https://go.dev/cl/761581

Vendor Advisories for CVE-2026-33814(8)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntucontainerd (1.7.24-0ubuntu1~20.04.2+esm2) @ focal2026-06-28ubuntu
ubuntugolang-github-containerd-containerd-dev (1.6.12-0ubuntu1~18.04.1+esm4) @ bionic2026-06-28ubuntu
ubuntucontainerd-stable (2.1.6-0ubuntu1~25.10.2) @ questing2026-06-28ubuntu
ubuntuadsys-windows (0.16.4ubuntu1.1) @ resolute2026-06-28ubuntu
redhatgolang1-25-main-1.25.11-2.hum12026-06-04redhat
redhatgolang1-26-main-1.26.4-2.hum12026-06-04redhat

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

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
golang.org/x/net—0.53.0—
stdlib—1.26.3—

Weakness Classification(2)

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-33814?
CVE-2026-33814 is a high vulnerability published on May 7, 2026. When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGSMAXFRAME_SIZE with a value of 0.
When was CVE-2026-33814 disclosed?
CVE-2026-33814 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33814 actively exploited?
CVE-2026-33814 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 51.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33814?
CVE-2026-33814 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33814?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33814, 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-33814

Explore →

Is Your Infrastructure Affected by CVE-2026-33814?

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

Start Free Scan →Browse All CVEs