# CVE-2024-30260: Undici's Proxy-Authorization header not cleared on cross-origin redirect for dispatch, request, stream, pipeline

> Attackers can steal sensitive authentication headers when using specific Undici methods during cross-origin redirects.

- **Severity:** Low 3.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Apr 2024
- **Updated:** 4 Nov 2025
- **Also known as:** AZL-39734, AZL-39803, DEBIAN-CVE-2024-30260, GHSA-m4v8-wqvr-p9f7, ROOT-APP-NPM-CVE-2024-30260, ROOT-OS-DEBIAN-12-CVE-2024-30260, UBUNTU-CVE-2024-30260, openSUSE-SU-2024:13850-1

## What is CVE-2024-30260?

CVE-2024-30260 is a low-severity vulnerability in Fedoraproject Fedora, published on 4 Apr 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici cleared Authorization and Proxy-Authorization headers for `fetch()`, but did not clear them for `undici.request()`. This vulnerability was patched in version(s) 5.28.4 and 6.11.1.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2024-30260?

4 open source packages ship an affected version, including undici. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `undici` | npm | All versions | 5.28.4 |
| `undici` | npm | All versions | 5.28.4 |
| `undici` | npm | From 6.0.0 | 6.11.1 |
| `undici` | npm | From 6.0.0 | 6.11.1 |
| `nodejs-electron` | openSUSE:Tumbleweed | All versions | 28.2.10-2.1 |

Products: Fedoraproject Fedora, Nodejs Undici.

## How do I fix CVE-2024-30260?

Upgrade undici to a fixed version for your release line: 5.28.4 or 6.11.1.

## Is CVE-2024-30260 being exploited?

There is no known exploitation of CVE-2024-30260 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30260 and fix it if it is affected.

What it is: CVE-2024-30260 is a low-severity vulnerability in Fedoraproject Fedora, published on 4 Apr 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-30260 in the wild and no public exploit code.

Affected packages and fixed versions:
- undici (npm): affected all versions; fixed in 5.28.4
- undici (npm): affected all versions; fixed in 5.28.4
- undici (npm): affected from 6.0.0; fixed in 6.11.1
- undici (npm): affected from 6.0.0; fixed in 6.11.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-30260/ (Markdown: https://insights.sbomify.com/CVE-2024-30260/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-30260
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-30260
- OSV: https://osv.dev/vulnerability/CVE-2024-30260

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-30260/
Summaries are generated and may contain mistakes; the official description above is the record.