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

Follow Redirects improperly handles URLs in the url.parse() functionGHSA-jchw-25xp-jwwc

MEDIUMFix: follow-redirects/follow-redirects#236

GHSA-jchw-25xp-jwwc is a medium-severity (CVSS 6.1) Improper Input Validation vulnerability in follow-redirects. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for follow-redirects — see the affected versions and patch details below.

Also known asCVE-2023-26159
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 6, 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-jchw-25xp-jwwc.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk
0.00%0.43%0.86%1.30%0.1%0.8%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
144.0Mdownloads / week

Description

Versions of the package follow-redirects before 1.15.4 are vulnerable to Improper Input Validation due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.

Affected Packages

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

Affected Products

1 product · 1 configurations
Application
follow redirectsfollow-redirects
< 1.15.4
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jchw-25xp-jwwc is resolved across your whole dependency graph.

  3. Workarounds

    Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

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

follow-redirects is a transitive dependency of Grafana, and does not affect Red Hat Enterprise Linux 8.

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-jchw-25xp-jwwc (CC BY 4.0)
ProductFixed inAdvisory
Migration Toolkit for Virtualization 2.5migration-toolkit-virtualization/mtv-console-plugin-rhel9:2.5.5-3RHBA-2024:0928
MTA-6.2-RHEL-8mta/mta-rhel8-operator:6.2.2-3RHSA-2024:1027
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
MTR 1.2.4follow-redirectsRHSA-2024:0720
multicluster engine for Kubernetes 2.4 for RHEL 8multicluster-engine/console-mce-rhel8:v2.4.5-25RHBA-2024:3555
NETWORK-OBSERVABILITY-1.5.0-RHEL-9network-observability/network-observability-console-plugin-rhel9:v1.5.0-89RHSA-2024:0853
Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8rhacm2/console-rhel8:v2.9.4-22RHBA-2024:3593

Frequently Asked Questions

Versions of the package follow-redirects before 1.15.4 are vulnerable to Improper Input Validation due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.
O3 Security · Impact-Aware SCA

Is GHSA-jchw-25xp-jwwc in your dependencies?

Find it across npm, including transitive dependencies.

Follow Redirects improperly handles URLs in the…