Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

GHSA-r683-j2x4-v87g node-fetch

HIGHFix: node-fetch/node-fetch#1449

GHSA-r683-j2x4-v87g is a high-severity (CVSS 8.8) Information Exposure vulnerability in node-fetch. 1 public exploit reference exists, so weaponization risk is real. A fix is available for node-fetch — see the affected versions and patch details below.

node-fetch forwards secure headers to untrusted sites

Also known asCVE-2022-0235
Published
Jan 21, 2022
Updated
Nov 8, 2023
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-r683-j2x4-v87g plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs 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.

45Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
node-fetchnpm
176.4Mdownloads / week

Description

node-fetch forwards secure headers such as authorization, www-authenticate, cookie, & cookie2 when redirecting to a untrusted site.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmnode-fetch3.0.0&&< 3.1.13.1.1npm install node-fetch@3.1.1
📦npmnode-fetchall versions2.6.7npm install node-fetch@2.6.7
Exploits & PoCs
1

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 node-fetch, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update node-fetch to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r683-j2x4-v87g is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r683-j2x4-v87g can be triaged on real exposure rather than presence alone.

Tailored to GHSA-r683-j2x4-v87g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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

This flaw is out of support scope for dotnet-5.0. For more information about Dotnet product support scope, please see https://access.redhat.com/support/policy/updates/net-core

ProductFixed inAdvisory
OpenShift Service Mesh 2.1openshift-service-mesh/kiali-rhel8:1.36.9-1RHSA-2022:1739
Red Hat Data Grid 8.4.0node-fetchRHSA-2022:8524
Red Hat Enterprise Linux 8nodejs:14-8070020221212161539.bd1311edRHSA-2023:0050
Red Hat Enterprise Linux 8.6 Extended Update Supportnodejs:14-8060020230306170237.ad008a3aRHSA-2023:1742
Red Hat Migration Toolkit for Containers 1.7rhmtc/openshift-migration-ui-rhel8:v1.7.2-9RHSA-2022:5483
Red Hat OpenShift Container Platform 4.11openshift4/ose-thanos-rhel8:v4.11.0-202208020235.p0.gf08da2d.assembly.streamRHSA-2022:5069
Red Hat OpenShift Data Foundation 4.11 on RHEL8odf4/mcg-core-rhel8:v4.11.0-30RHSA-2022:6156
Red Hat Software Collections for Red Hat Enterprise Linux 7rh-nodejs14-nodejs-0:14.21.1-3.el7RHSA-2023:0612
UbuntuMEDIUM

Frequently Asked Questions

node-fetch forwards secure headers such as `authorization`, `www-authenticate`, `cookie`, & `cookie2` when redirecting to a untrusted site.
O3 Security · Impact-Aware SCA

Is GHSA-r683-j2x4-v87g in your dependencies?

O3 Security finds GHSA-r683-j2x4-v87g across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-r683-j2x4-v87g: node-fetch (High 8.8) | O3 Security