Affected: Go standard library net/http

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.

Affected: Ubuntu:22.04:LTS: golang-1.22, Ubuntu:24.04:LTS: golang-1.22

Kyle Seely discovered that the Go net/http module did not properly handle sensitive headers during repeated redirects. An attacker could possibly use this issue to obtain sensitive information. (CVE-2024-45336)

Juho Forsén discovered that the Go crypto/x509 module incorrectly handled IPv6 addresses during URI parsing. An attacker could possibly use this issue to bypass certificate URI constraints. (CVE-2024-45341)

It was discovered that the Go crypto module did not properly handle variable time instructions under certain circumstances on 64-bit Power (ppc64el) systems. An attacker could possibly use this issue to expose sensitive information. (CVE-2025-22866)

It was discovered that the Go http/httpproxy module did not properly handle IPv6 zone IDs during hostname matching. An attacker could possibly use this issue to cause a denial of service. (CVE-2025-22870)

Takeshi Kaneko discovered that the Go net/http module did not properly strip sensitive proxy headers during redirect requests. An attacker could possibly use this issue to obtain sensitive information. (CVE-2025-4673)