Is CVE-2026-33814 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-33814 being exploited in the wild.

How severe is CVE-2026-33814?

High severity, with a CVSS score of 7.5, published 7 May 2026.

Which products and versions are affected?

golang.org/x/net (Go) SEMVER:introduced=0,fixed=0.53.0; stdlib (Go) SEMVER:introduced=0,fixed=1.25.10,introduced=1.26.0-0,fixed=1.26.3; Go Project Go http2 package before v0.53.0; Google X/Net/Http2 < 0.53.0.

Is there a fix for CVE-2026-33814?

Yes. golang.org/x/net (Go): upgrade to 0.53.0 or later; stdlib (Go): upgrade to 1.26.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-33814 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-33814?

Check whether you run golang.org/x/net (Go), stdlib (Go), Go Project Go http2 package or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33814: Go net/http infinite loop in HTTP/2 SETTINGS frame processing

Q: Is there a fix for CVE-2026-33814?

Yes. golang.org/x/net (Go): upgrade to 0.53.0 or later; stdlib (Go): upgrade to 1.26.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-33814 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-33814?

Check whether you run golang.org/x/net (Go), stdlib (Go), Go Project Go http2 package or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33814 · Severity: high · CVSS 7.5 · Published 2026-05-07

A vulnerability in the Go programming language's networking library can allow a malicious server to crash or freeze a client application. By sending a specially crafted HTTP/2 configuration message, the server forces the client into an infinite processing loop. This results in a denial-of-service (DoS) condition, making the affected application unresponsive and consuming system resources.

Technologies: golang.org/x/net (Go), stdlib (Go). Vendors: Go, Go Project, Google.

Quick answers

Is CVE-2026-33814 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-33814 being exploited in the wild.
How severe is CVE-2026-33814?: High severity, with a CVSS score of 7.5, published 7 May 2026.
Which products and versions are affected?: golang.org/x/net (Go) SEMVER:introduced=0,fixed=0.53.0; stdlib (Go) SEMVER:introduced=0,fixed=1.25.10,introduced=1.26.0-0,fixed=1.26.3; Go Project Go http2 package before v0.53.0; Google X/Net/Http2 < 0.53.0.
Is there a fix for CVE-2026-33814?: Yes. golang.org/x/net (Go): upgrade to 0.53.0 or later; stdlib (Go): upgrade to 1.26.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33814 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-33814?: Check whether you run golang.org/x/net (Go), stdlib (Go), Go Project Go http2 package or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

golang.org/x/net (Go): upgrade to 0.53.0 or later
```
go get golang.org/x/net@v0.53.0
```
stdlib (Go): upgrade to 1.26.3 or later
```
go get stdlib@v1.26.3
```

Technical details

A denial-of-service vulnerability exists in the Go net/http and golang.org/x/net/http2 packages. The root cause is an 'Infinite Loop' (CWE-835) triggered when the HTTP/2 transport receives a SETTINGS frame containing a SETTINGS_MAX_FRAME_SIZE value of 0. This causes the transport to enter a loop continuously writing CONTINUATION frames. An unauthenticated remote attacker acting as a malicious server can exploit this against any Go-based client using the affected HTTP/2 transport. The issue is resolved in Go versions 1.25.10 and 1.26.3, and x/net/http2 version v0.53.0.

Affected products

Go Project Go net/http before 1.25.10, from 1.26.0-0 before 1.26.3
Go Project golang.org/x/net/http2 before v0.53.0
Red Hat Red Hat Enterprise Linux 8, 9, 10
Red Hat Red Hat OpenShift Container Platform 4

Identifiers

CVE-2026-33814
GO-2026-4918

Timeline

2026-03-31: disclosed: Issue reported to Go project via GitHub
2026-05-07: advisory: NVD and Go vulnerability report published
2026-06-04: patched: Red Hat released security advisories for affected products

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.