Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
20 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.
Recommended action: Upgrade to 1.27.3 or 1.26.10 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
On Windows, when the target of Root.Mkdir or Root.MkdirAll is a junction pointing to an empty location, the operation can create a directory at the junction target even when that target is located outside the root. This only applies to operations where the last path component is a junction (path/to/junction, but not path/junction/target).
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When a JavaScript template literal contains consecutive expressions, the context tracking state was not properly reset upon entering a new expression. We now ensure that template-literal expression entries correctly reset context variables so all subsequent regular expression literals are accurately recognized and escaped.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 SETTINGS_INITIAL_WINDOW_SIZE values.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.
Recommended action: Upgrade to 1.27.2 or 1.26.9 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion.
Recommended action: Upgrade to 1.27.0-rc.3 (pre-release), 1.26.6 or 1.25.13 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this.
Recommended action: Upgrade to 1.27.0-rc.3 (pre-release), 1.26.6 or 1.25.13 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures.
Recommended action: Upgrade to 1.27.0-rc.3 (pre-release), 1.26.6 or 1.25.13 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely.
Recommended action: Upgrade to 1.27.0-rc.3 (pre-release), 1.26.6 or 1.25.13 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte buffer using index-based backtracking for '..' segments, eliminating the quadratic time complexity and significantly reducing memory allocations.
Recommended action: Upgrade to 1.27.0-rc.3 (pre-release), 1.26.6 or 1.25.13 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Previously, pathological inputs could close an unescaped '/' early, allowing for attack-controlled data to inject arbitrary content, potentially leading to XSS.
Recommended action: Upgrade to 1.27.0-rc.3 (pre-release), 1.26.6 or 1.25.13 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.