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 46% 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.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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

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%
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

Published

May 7, 2026

Last Modified

September 18, 2026

Advisory Details (5)

Auto-updated May 8, 2026
Patch available.
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(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatose-crio-credential-provider-0:4.21.0-202609021357.p2.g83d4961.assembly.stream.el102026-09-15redhat
redhatopenshift4/ose-thanos-rhel8:17882194272026-09-11redhat
redhatopenshift4/ose-prometheus-rhel9:17881641752026-09-10redhat
redhatopenshift4/ose-gcp-filestore-csi-driver-rhel9:17881543242026-09-10redhat
redhatopenshift4/ose-sriov-network-device-plugin-rhel9:17883105402026-09-09redhat
redhatopenshift4/ose-vsphere-problem-detector-rhel9:17883100792026-09-09redhat
redhatmicroshift-0:4.19.46-202609041024.p0.g59e34c7.assembly.4.19.46.el92026-09-09redhat
redhatrhoai/odh-trustyai-service-operator-rhel9:17873300732026-09-08redhat
redhatmicroshift-0:4.20.37-202609041024.p0.g3d0d639.assembly.4.20.37.el92026-09-08redhat
redhatmicroshift-0:4.22.13-202609041025.p0.g0d02d40.assembly.4.22.13.el92026-09-08redhat
redhatopenshift4/kube-compare-artifacts-rhel9:17883495702026-09-08redhat
redhatose-crio-credential-provider-0:4.22.0-202608271248.p2.g83d4961.assembly.stream.el82026-09-08redhat
redhatopenshift4/ose-sriov-network-device-plugin-rhel9:17882749512026-09-08redhat
redhatopenshift4/ose-vsphere-problem-detector-rhel9:17883031452026-09-08redhat
redhatopenshift4/ose-vsphere-problem-detector-rhel9:17881997072026-09-08redhat
redhatopenshift4/kube-compare-artifacts-rhel9:17883139882026-09-08redhat
redhatopenshift4/ose-vsphere-problem-detector-rhel9:17882734272026-09-08redhat
redhatopenshift4/ose-cluster-capacity-rhel9:17875481142026-09-03redhat
redhatopenshift4/ose-thanos-rhel8:17867521762026-09-03redhat
redhatopenshift4/ose-prometheus-rhel9:17875568642026-09-03redhat
redhatopenshift4/ose-prometheus-rhel9:17875521222026-09-02redhat
redhatopenshift4/ose-gcp-filestore-csi-driver-rhel9:17877412592026-09-01redhat
redhatopenshift4/ose-prometheus-rhel9:17877361832026-09-01redhat
redhatopenshift4/ose-prometheus-rhel9:17875595772026-09-01redhat
redhatmicroshift-0:4.21.31-202608272317.p0.ge6439cf.assembly.4.21.31.el92026-09-01redhat
redhatopenshift4/ose-gcp-filestore-csi-driver-rhel9:17877579172026-09-01redhat
redhatopenshift4/ose-tools-rhel9:17877224892026-09-01redhat
redhatopenshift4/ose-cluster-capacity-rhel9:17875575482026-09-01redhat
redhatgolang-0:1.26.5-1.el9_22026-08-31redhat
redhatrhoai/odh-workload-variant-autoscaler-controller-rhel9:17875622002026-08-27redhat

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 rangeFix by version rangeDependents
golang.org/x/net—
  • every version up to 0.53.0: fixed in 0.53.0
—
stdlib—
  • every version up to 1.25.10: fixed in 1.25.10
  • 1.26.0-0 up to 1.26.3: fixed in 1.26.3
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-net1:0.0+git20210119.5f4716e+dfsg-4 ... 1:0.7.0+dfsg-1 (40 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-net1:0.10.0-1 ... 1:0.7.0+dfsg-1 (27 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-net1:0.27.0-2 ... 1:0.58.0-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-net1:0.27.0-2, 1:0.47.0-1, 1:0.47.0-2
  • every version up to 1:0.53.0-1: fixed in 1:0.53.0-1
—

Weakness Classification(2)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 48× 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 317 total refreshes for this CVE.

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

Related CVEs(same product + 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 on May 7, 2026, with the most recent update on September 18, 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 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-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?
A fix for CVE-2026-33814 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-33814 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-33814

Explore →

Is Your Infrastructure Affected by CVE-2026-33814?

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

Book a Demo →Browse All CVEs