Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-vp56-6g26-6827

MEDIUM

GHSA-vp56-6g26-6827 is a medium-severity (CVSS 5.9) CWE-1333 vulnerability in node-fetch. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-vp56-6g26-6827 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

node-fetch Inefficient Regular Expression Complexity

Also known asCVE-2022-2596
Published
Aug 2, 2022
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

node-fetchnpm
179.1Mdownloads / week

Description

node-fetch is a light-weight module that brings window.fetch to node.js.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) in the isOriginPotentiallyTrustworthy() function in referrer.js, when processing a URL string with alternating letters and periods, such as 'http://' + 'a.a.'.repeat(i) + 'a'.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmnode-fetch3.0.0&&< 3.2.103.2.10
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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update node-fetch to 3.2.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vp56-6g26-6827 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 pinpoints whether GHSA-vp56-6g26-6827 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vp56-6g26-6827. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

[node-fetch](https://www.npmjs.com/package/node-fetch) is a light-weight module that brings window.fetch to node.js. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) in the `isOriginPotentiallyTrustworthy()` function in `referrer.js`, when processing a URL string with alternating letters and periods, such as `'http://' + 'a.a.'.repeat(i) + 'a'`.
O3 Security · Impact-Aware SCA

Is GHSA-vp56-6g26-6827 in your dependencies?

O3 detects GHSA-vp56-6g26-6827 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.