LowGHSA-m4v8-wqvr-p9f7CVE-2024-30260

Undici's Proxy-Authorization header not cleared on cross-origin redirect for dispatch, request, stream, pipeline

Published 4 Apr 2024 · Updated 4 Nov 2025

Affected packages

Affected
<5.28.4
Fixed in
5.28.4
Update to the fixed version for your release line, for example:npm install undici@5.28.4
Affected
>=6.0.0 <6.11.1
Fixed in
6.11.1
Update to the fixed version for your release line, for example:npm install undici@6.11.1

Details

Impact

Undici cleared Authorization and Proxy-Authorization headers for fetch(), but did not clear them for undici.request().

Patches

This has been patched in https://github.com/nodejs/undici/commit/6805746680d27a5369d7fb67bc05f95a28247d75. Fixes has been released in v5.28.4 and v6.11.1.

Workarounds

use fetch() or disable maxRedirections.

References

Linzi Shang reported this.

  • https://hackerone.com/reports/2408074
  • https://github.com/nodejs/undici/security/advisories/GHSA-3787-6prv-h9w3

Is GHSA-m4v8-wqvr-p9f7 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected undici, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.