GO-2026-4918 is no longer reported for csi-hcloud in the newest 1.36 release (v10). View csi-hcloud in v10
GO-2026-4918
GoInfinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net
Our assessment
This flaw can hang a program only when it connects out to a malicious server. The affected components connect only to trusted internal services, so no attacker-run server is reached.
Syself Security- OSV: https://osv.dev/vulnerability/GO-2026-4918
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33814
- upstream issue golang/go#78476: https://github.com/golang/go/issues/78476
- x/net upstream fix commit: https://go-review.googlesource.com/c/net/+/761640
- Debian security tracker: https://security-tracker.debian.org/tracker/CVE-2026-33814
GO-2026-4918
GoInfinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net
Our assessment
This flaw can hang a program only when it connects out to a malicious server. The affected parts connect only to trusted internal services, never to servers a tenant controls, so the flaw cannot be triggered.
Syself Security- OSV: https://osv.dev/vulnerability/GO-2026-4918
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33814
- upstream issue golang/go#78476: https://github.com/golang/go/issues/78476
- upstream fix (x/net): https://go-review.googlesource.com/c/net/+/761640
- Debian security tracker: https://security-tracker.debian.org/tracker/CVE-2026-33814
GO-2026-4918
GoInfinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net
Our assessment
This flaw can freeze a program, but only when it connects out to a harmful server. The affected programs connect out only to known, trusted services, so no attacker-run server can trigger it.
Syself SecurityGO-2026-4918
GoInfinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net
Our assessment
This flaw lets a harmful server make a program that connects to it stop responding. The affected parts connect only to trusted internal services, never to a server an attacker controls, so they cannot be made to stop responding.
Syself Security- OSV: https://osv.dev/vulnerability/GO-2026-4918
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33814
- upstream issue golang/go#78476: https://github.com/golang/go/issues/78476
- upstream fix commit (x/net): https://go-review.googlesource.com/c/net/+/761640
- Debian security tracker: https://security-tracker.debian.org/tracker/CVE-2026-33814