CVE-2024-45336: Golang 1.10 · The HTTP client drops sensitive headers after following a cross-domain redirect
Affects golang-1.10Source GCVE Database
Not known to be exploited · CVSS 6.1 Medium · fixed in 1.22.2-2~22.04.3 : update golang-1.10 when convenient.
Data as of 17 Nov 2026, 20:35 UTC
- Patch
- Available – fixed in 1.22.2-2~22.04.3, 1.22.2-2ubuntu0.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade the Ubuntu golang-1.22 to 1.22.2-2~22.04.3 (package) or 1.22.2-2ubuntu0.4 (package).
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSgolang-1.24pkg:deb/ubuntu/golang-1.24?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 25.10golang-1.24pkg:deb/ubuntu/golang-1.24?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSgolang-1.21pkg:deb/ubuntu/golang-1.21?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSgolang-1.22pkg:deb/ubuntu/golang-1.22?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSgolang-1.23pkg:deb/ubuntu/golang-1.23?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSgolang-1.17pkg:deb/ubuntu/golang-1.17?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.