# CVE-2024-28849: Proxy-Authorization header kept across hosts in follow-redirects

> The follow-redirects library leaks Proxy-Authorization credentials to unintended hosts during redirects, requiring an upgrade to prevent credential exposure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Mar 2024
- **Updated:** 13 Feb 2025
- **Also known as:** AZL-36895, AZL-43861, AZL-44493, CLSA-2026-1776818198, DEBIAN-CVE-2024-28849, GHSA-cxjh-pqwp-8mfp, UBUNTU-CVE-2024-28849

## What is CVE-2024-28849?

CVE-2024-28849 is a medium-severity vulnerability in follow-redirects, published on 14 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

follow-redirects is an open source, drop-in replacement for Node's `http` and `https` modules that automatically follows redirects. In affected versions follow-redirects only clears authorization header during cross-domain redirect, but keep the proxy-authentication header which contains credentials too. This vulnerability may lead to credentials leak, but has been addressed in version 1.15.6. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

2 open source packages ship an affected version, including follow-redirects. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `follow-redirects` | npm | All versions | 1.15.6 |
| `follow-redirects` | npm | All versions | 1.15.6 |

Products: Follow-Redirects Project Follow-Redirects.

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

Upgrade follow-redirects to 1.15.6 or later.

## Is CVE-2024-28849 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28849 exists.

## Other vulnerabilities in follow-redirects

- [CVE-2022-0155](https://insights.sbomify.com/CVE-2022-0155/): Exposure of Private Personal Information to an Unauthorized Actor in follow-redirects/follow-redirects (high 8.0)
- [CVE-2026-40895](https://insights.sbomify.com/CVE-2026-40895/): follow-redirects: Custom Authentication Headers Leaked to Cross-Domain Redirect Targets (medium 6.9)
- [CVE-2022-0536](https://insights.sbomify.com/CVE-2022-0536/): Improper Removal of Sensitive Information Before Storage or Transfer in follow-redirects/follow-redirects (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28849 is a medium-severity vulnerability in follow-redirects, published on 14 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28849 exists.

Affected packages and fixed versions:
- follow-redirects (npm): affected all versions; fixed in 1.15.6
- follow-redirects (npm): affected all versions; fixed in 1.15.6

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-28849/ (Markdown: https://insights.sbomify.com/CVE-2024-28849/index.md)
```

## Sources

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

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