NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

follow-redirects' Proxy-Authorization header kept across hostsGHSA-cxjh-pqwp-8mfp

MEDIUMFix: follow-redirects/follow-redirects@c4f847f

GHSA-cxjh-pqwp-8mfp is a medium-severity (CVSS 6.5) Information Exposure vulnerability in follow-redirects. A fix is available for follow-redirects — see the affected versions and patch details below.

Also known asCVE-2024-28849
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cxjh-pqwp-8mfp.

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk
0.44%0.83%1.22%1.61%0.9%1.0%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
follow-redirectsnpm
143.1Mdownloads / week

Description

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:

const axios = require('axios');

axios.get('http://127.0.0.1:10081/', {
 headers: {
 'AuThorization': 'Rear Test',
 'ProXy-AuthoriZation': 'Rear Test',
 'coOkie': 't=1'
 }
})
 .then((response) => {
 console.log(response);
 })

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

- removeMatchingHeaders(/^(?:authorization|cookie)$/i, this._options.headers);
+ removeMatchingHeaders(/^(?:authorization|proxy-authorization|cookie)$/i, this._options.headers);

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmfollow-redirectsall versions1.15.6npm install follow-redirects@1.15.6

Affected Products

1 product · 1 configurations
Application
follow-redirectsfollow-redirects_project
< 1.15.6
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for follow-redirects, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update follow-redirects to 1.15.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cxjh-pqwp-8mfp is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
HawtIO 4.0.0 for Red Hat build of Apache Camel 4follow-redirectsRHSA-2024:3550
Migration Toolkit for Runtimes 1 on RHEL 8follow-redirectsRHSA-2024:3920
MTA-6.2-RHEL-9mta/mta-ui-rhel9:6.2.3-2RHSA-2024:3989
MTA-7.0-RHEL-9mta/mta-cli-rhel9:7.0.3-16RHSA-2024:3316
multicluster engine for Kubernetes 2.5 for RHEL 9multicluster-engine/console-mce-rhel9:v2.5.3-7RHBA-2024:2862
NETWORK-OBSERVABILITY-1.6.0-RHEL-9network-observability/network-observability-cli-rhel9:v1.6.0-66RHSA-2024:3868
OpenShift-Pipelines-1.15-RHEL-8openshift-pipelines/pipelines-chains-controller-rhel8:v1.15.0-18RHEA-2024:3997
Red Hat Advanced Cluster Management for Kubernetes 2.10 for RHEL 9rhacm2/console-rhel9:v2.10.2-3RHBA-2024:2034

Frequently Asked Questions

When using [axios](https://github.com/axios/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: ```js const axios = require('axios'); axios.get('http://127.0.0.1:10081/', { headers: { 'AuThorization': 'Rear Test', 'ProXy-AuthoriZation': 'Rear Test', 'coOkie': 't=1' } }) .then((response) => { console.log(response); }) ``` When I meet the cross-domain redirect, the sensitive headers like authorization and cookie are clea
O3 Security · Impact-Aware SCA

Is GHSA-cxjh-pqwp-8mfp in your dependencies?

Find it across npm, including transitive dependencies.

follow-redirects' Proxy-Authorization header kept across…