147781 matches found
CVE-2026-78669 Excessive CPU consumption from repeated initial window changes in net/http
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGSINITIALWINDOWSIZE values...
CVE-2026-78669
A malicious HTTP/2 peer can trigger excessive CPU consumption in a client or server by opening numerous streams and transmitting many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. This vulnerability impacts several packages, including loki , cloud-sql-proxy , kube-bench , ...
CVE-2026-78669
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGSINITIALWINDOWSIZE values...
CVE-2026-78667 Lack of limit on size of parsed Range headers in net/http
When parsing a Range header containing a large number of small ranges, FileServerFS, ServeContent, and ServeFileFS can consume an excessive amount of CPU...
CVE-2026-78669
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGSINITIALWINDOWSIZE values...
CVE-2026-78667
The FileServer(FS) , ServeContent , and ServeFile(FS) components are vulnerable to a CPU exhaustion issue. This occurs when parsing a Range header that contains a large number of small ranges, leading to excessive resource consumption. This vulnerability is associated with CWE-770 (Allocation of ...
CVE-2026-56866 HTTP/1 client connection desynchronization after CONNECT rejection in net/http
When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle...
EUVD-2026-95419
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 malicious client can exploit this by sending ...
CVE-2026-78659
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 malicious client can exploit this by sending ...
CVE-2026-56866 HTTP/1 client connection desynchronization after CONNECT rejection in net/http
When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle...
CVE-2026-56866
The http.Transport component is vulnerable to a desynchronization issue when handling HTTP/1 CONNECT requests with a non-empty Request.Body . The underlying cause is that the transport writes the body directly to the connection without framing; if a server rejects the request with a non-2xx keep-...
CVE-2026-78659
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 malicious client can exploit this by sending ...
CVE-2026-78659
An HTTP server is vulnerable to an asymmetric resource consumption attack via HTTP/2 "Trailer" headers. A malicious client can send a large number of fields within a "Trailer" header, forcing the server to allocate a disproportionate amount of memory because the Request.Trailer map incurs memory ...
CVE-2026-78659 HTTP/2 server memory exhaustion due to Trailer headers in net/http
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 malicious client can exploit this by sending ...
CVE-2026-78659 HTTP/2 server memory exhaustion due to Trailer headers in net/http
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 malicious client can exploit this by sending ...
CVE-2026-78659
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 malicious client can exploit this by sending ...
CVE-2026-107232
A flaw was found in AsyncHttpClient. When an HTTP proxy rejects an HTTPS CONNECT request, the client can incorrectly treat the still-plaintext connection to the proxy as an established tunnel. A subsequent proxy authentication challenge or redirect can cause the client to resend the origin reques...
CVE-2026-107279
A flaw was found in AsyncHttpClient. A remote attacker can bypass mutual authentication by offering HTTP Digest authentication configured with integrity protection auth-int. Because the client fails to validate the response authentication value under this configuration and treats the unverified...
CVE-2025-12999
A flaw was found in openvsx-server. This vulnerability allows an unauthenticated remote attacker to achieve arbitrary code execution on client machines through HTTP cache poisoning. The server generates download and verification URLs from untrusted proxy headers, such as X-Forwarded-Host, without...
GO-2026-6613 HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http
When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server...