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.8%, top 47% 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
Trending — Patch released 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: 1%CVSS: 7.5Exploit: None knownExposed: 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)
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%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

May 7, 2026

Last Modified

August 21, 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(20)

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

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntucontainerd-stable (2.2.2-0ubuntu1.1) @ resolute2026-08-21ubuntu
ubuntugolang-github-containerd-containerd-dev (1.6.12-0ubuntu1~18.04.1+esm4) @ bionic2026-08-21ubuntu
ubuntuadsys-windows (0.16.3~22.04.2ubuntu0.22.04.1) @ jammy2026-08-21ubuntu
ubuntucontainerd (2.2.1-0ubuntu1~24.04.3) @ noble2026-08-21ubuntu
redhatrhacm2/klusterlet-addon-controller-rhel9:17869083012026-08-19redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17869120062026-08-19redhat
redhatworkload-availability/node-healthcheck-rhel9-operator:17852027232026-08-12redhat
redhatworkload-availability/fence-agents-remediation-rhel9-operator:17852030792026-08-12redhat
redhatworkload-availability/self-node-remediation-rhel9-operator:17852030362026-08-12redhat
redhatworkload-availability/node-maintenance-rhel9-operator:17852028472026-08-12redhat
redhatworkload-availability/machine-deletion-remediation-rhel9-operator:17852035082026-08-12redhat
redhatworkload-availability/storage-based-remediation-rhel9-operator:17852034742026-08-12redhat
redhatrhosdt/opentelemetry-rhel9-operator:17857045472026-08-04redhat
redhatoadp/oadp-velero-rhel9:17840588222026-07-22redhat
redhatrhoai/odh-training-operator-rhel9:17839463862026-07-21redhat
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat
redhatcluster-observability-operator/monitoring-console-plugin-rhel9:17828384762026-07-01redhat
redhatopenshift-service-mesh/istio-rhel9-operator:17822224512026-06-29redhat
redhatopenshift-service-mesh/istio-rhel9-operator:17822245412026-06-29redhat
redhatopenshift-service-mesh/istio-rhel9-operator:17822220382026-06-29redhat
redhatopenshift-service-mesh/istio-rhel9-operator:17822226072026-06-29redhat
redhatgolang1-26-main-1.26.4-2.hum12026-06-04redhat
redhatgolang1-25-main-1.25.11-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

(6 across 5 ecosystems)
Go(2)
PackageVulnerable rangeFixed inDependents
golang.org/x/net—0.53.0—
stdlib—1.26.3—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-net1:0.0+git20210119.5f4716e+dfsg-4 ... 1:0.7.0+dfsg-1 (40 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-net1:0.10.0-1 ... 1:0.7.0+dfsg-1 (26 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-net1:0.27.0-2 ... 1:0.57.0-1 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-net1:0.27.0-2, 1:0.47.0-1, 1:0.47.0-21:0.53.0-1—

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 24× in last 7d / 95× 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 222 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 21, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 46.8% of all scored CVEs.
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