follow-redirects' Proxy-Authorization header kept across hosts

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-28849: 1.04% estimated exploitation activity in the next 30 days; percentile 64.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

When using axios, its dependency follow-redirects only clears authorization header during cross-domain redirect, but allows the proxy-authentication header which contains credentials too. Steps To Reproduce & PoC Test code: When I meet the cross-domain redirect, the sensitive headers like authorization and cookie are cleared, but proxy-authentication header is kept. Impact This vulnerability may lead to credentials leak. Recommendations Remove proxy-authentication header during cross-domain redirect Recommended Patch follow-redirects/index.js:464

Published by the source

14 Mar 2024, 17:19 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:30 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-cxjh-pqwp-8mfp

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-cxjh-pqwp-8mfp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-28849

Advisory: follow-redirects' Proxy-Authorization header kept across hosts
IDs: CVE-2024-28849, GHSA-cxjh-pqwp-8mfp
Record: https://patchnext.com/advisories/cve-2024-28849 (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: follow-redirects 1.15.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm follow-redirects: affected <= 1.15.5; fixed in 1.15.6

## Suggested inspection (read-only)
- `npm ls follow-redirects --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on follow-redirects.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-cxjh-pqwp-8mfp (OSV record GHSA-cxjh-pqwp-8mfp lists affected ranges: npm follow-redirects >=0 <1.15.6 (fixed))
- Verified: https://github.com/advisories/GHSA-cxjh-pqwp-8mfp (GitHub-reviewed advisory GHSA-cxjh-pqwp-8mfp lists affected ranges: npm follow-redirects >=0 <=1.15.5)

Commands are suggestions: review each one before running it.