15 results (0.007 seconds)

CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0

20 Jan 2026 — The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption. An update for the go-toolset:rhel8 module is now available for Red Hat Enterprise Linux 8. Issues addressed include a memory exhaustion vulnera... • https://go.dev/cl/736712 •

CVSS: 8.5EPSS: 0%CPEs: 2EXPL: 0

09 Oct 2025 — The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement. • https://go.dev/cl/709857 •

CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 0

09 Oct 2025 — Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does not have a limit. By sending a lot of very small cookies such as "a=;", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption. These are all security issues fixed in the regclient-0.10.0-1.1 package on the GA media of openSUSE Tumbleweed. • https://go.dev/cl/709855 •

CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 0

09 Oct 2025 — The Reader.ReadResponse function constructs a response string through repeated string concatenation of lines. When the number of lines in a response is large, this can cause excessive CPU consumption. These are all security issues fixed in the go1.25-1.25.2-1.1 package on the GA media of openSUSE Tumbleweed. • https://go.dev/cl/709859 •

CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0

09 Oct 2025 — The ParseAddress function constructeds domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption. The ParseAddress function constructs domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption. These are all security issues fixed in the go1.25-1.25.2-1.1 package on the GA media of openSUSE Tumbleweed. • https://go.dev/cl/709860 •

CVSS: 6.4EPSS: 0%CPEs: 1EXPL: 0

06 Sep 2025 — When using http.CrossOriginProtection, the AddInsecureBypassPattern method can unexpectedly bypass more requests than intended. CrossOriginProtection then skips validation, but forwards the original request path, which may be served by a different handler without the intended security protections. These are all security issues fixed in the go1.25-1.25.1-1.1 package on the GA media of openSUSE Tumbleweed. • https://go.dev/cl/699275 •

CVSS: 6.8EPSS: 0%CPEs: 2EXPL: 0

09 Jun 2025 — Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information. A flaw was found in net/http. Handling Proxy-Authorization and Proxy-Authenticate headers during cross-origin redirects allows these headers to be inadvertently forwarded, potentially exposing sensitive authentication credentials. This flaw allows a network-based attacker to manipulate redirect responses, unintentionally exposing authentication details to unauthorized parties. Ky... • https://go.dev/cl/679257 •

CVSS: 9.4EPSS: 0%CPEs: 2EXPL: 0

04 Apr 2025 — The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext. A flaw was found in the net/http golang package. The net/http package incorrectly accepts messages that end with a line feed (LF) instead of the proper line ending. When used with another server that also misinterprets this, it can lead to request smugglin... • https://go.dev/cl/652998 • CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') •

CVSS: 6.1EPSS: 0%CPEs: 3EXPL: 0

28 Jan 2025 — The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2. A flaw was found in the net/http... • https://go.dev/cl/643100 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0

02 Jul 2024 — 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 request sent on the connection will fail. An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational respon... • https://go.dev/cl/591255 • CWE-20: Improper Input Validation •