Undici's Proxy-Authorization header not cleared on cross-origin redirect for dispatch, request, stream, pipeline
Affects undiciSource GCVE Database
Not known to be exploited · CVSS 3.9 Low : upgrade to 5.28.4 when convenient.
Data as of 4 Nov 2026, 17:27 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 3.9 |
|---|
- Patch
- Available – fixed in 5.28.4, 6.11.1
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 4 Apr 2024
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 4 Nov 2026.
What to do
Upgrade undici to 5.28.4; undici to 6.11.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmundici | Affected
| Fixed in
|
| npmundici | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Undici to version 5.28.4 or later, or 6.11.1 or later, where the issue is fixed. Alternatively, use the fetch() API which already clears these headers correctly, or disable maxRedirections to prevent automatic redirects that trigger the vulnerability.
Description
Undici, a Node.js HTTP client, had a vulnerability where the Proxy-Authorization header was not cleared on cross-origin redirects for certain request methods like undici.request(), unlike fetch() which cleared these headers. This could lead to unintended credential exposure during redirects. The issue has been patched in versions 5.28.4 and 6.11.1. Users are advised to upgrade to these versions or use fetch() or disable maxRedirections as a workaround.
References
- github.com/nodejs/undici/security/advisories/GHSA-m4v8-wqvr-p9f7 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2024-30260 (opens in a new tab)
- github.com/nodejs/undici/commit/64e3402da4e032e68de46acb52800c9a06aaea3f (opens in a new tab)
- github.com/nodejs/undici/commit/6805746680d27a5369d7fb67bc05f95a28247d75 (opens in a new tab)
- hackerone.com/reports/2408074 (opens in a new tab)
- github.com/nodejs/undici (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HQVHWAS6WDXXIU7F72XI55VZ2LTZUB33 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NC3V3HFZ5MOJRZDY5ZELL6REIRSPFROJ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P6Q4RGETHVYVHDIQGTJGU5AV6NJEI67E (opens in a new tab)
- security.netapp.com/advisory/ntap-20240905-0008 (opens in a new tab)