Go standard library net/http Schwachstellen (CVE)

Für Go standard library net/http veröffentlichte CVE-Einträge, neueste zuerst. Folgen Sie, um bei neuen Einträgen eine E-Mail zu erhalten.

27 Ergebnisse
5.9Mittel
CVE-2026-97054

HTTP/1 server crash due to MaxBytesReader header race in net/http

Go standard library net/http

For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes …

7.5Hoch
CVE-2026-97032

HTTP/2 server crash due to HPACK encoder race in net/http

Go standard library net/http; Go standard library net/http/internal/http2; golang.org/x/net golang.org/x/net/http2

HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part …

9.1Kritisch
CVE-2026-78663

Double flow control refund on HTTP/2 server streams in net/http

Go standard library net/http; Go standard library net/http/internal/http2; golang.org/x/net golang.org/x/net/http2

The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client…

7.5Hoch
CVE-2026-78660

HTTP/2 transport accepts malformed framing-related headers in net/http

Go standard library net/http; Go standard library net/http/internal/http2; golang.org/x/net golang.org/x/net/http2

Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such header…

7.5Hoch
CVE-2026-78659

HTTP/2 server memory exhaustion due to Trailer headers in net/http

Go standard library net/http; Go standard library net/http/internal/http2; golang.org/x/net golang.org/x/net/http2

When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicio…

9.6Kritisch
CVE-2026-39821

Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna

Go standard library net/http; Go standard library net/http/internal/http2; golang.org/x/net golang.org/x/net/idna; Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 8

The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error. This behavior can lead to privilege …

1.8%EPSS
4.4Mittel
CVE-2025-22870

HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net

Go standard library net/http; golang.org/x/net golang.org/x/net/http/httpproxy; golang.org/x/net golang.org/x/net/proxy

Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.

7.5Hoch
CVE-2024-24791

Denial of service due to improper 100-continue handling in net/http

Go standard library net/http; go_standard_library net\/http

The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next r…

1.4%EPSS
7.5Hoch
CVE-2023-45288

HTTP/2 CONTINUATION flood in net/http

Go standard library net/http; golang.org/x/net golang.org/x/net/http2; go_standard_library net\/http; golang http2

An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a reques…

89%EPSS
Ohne Score
CVE-2023-39325

HTTP/2 rapid reset can cause excessive work in net/http

Go standard library net/http; golang.org/x/net golang.org/x/net/http2

A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress requ…

3.8%EPSS
Ohne Score
CVE-2023-29406

Insufficient sanitization of Host header in net/http

Go standard library net/http

The HTTP/1 client does not fully validate the contents of the Host header. A maliciously crafted Host header can inject additional headers or entire requests. With fix, the HTTP/1 client now refuses to send requests containing an invalid Request.Host or Reque…

1.5%EPSS
Ohne Score
CVE-2022-41717

Excessive memory growth in net/http and golang.org/x/net/http2

Go standard library net/http; golang.org/x/net golang.org/x/net/http2

An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large…

6.2%EPSS
7.5Hoch
CVE-2022-41720

Restricted file access on Windows in os and net/http

Go standard library os; Go standard library net/http

On Windows, restricted files can be accessed via os.DirFS and http.Dir. The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, …

1.3%EPSS