GHSA-w7rc-rwvf-8q5r
LOWGHSA-w7rc-rwvf-8q5r is a low-severity (CVSS 2.6) Improper Input Validation vulnerability in node-fetch. O3 Security confirms whether GHSA-w7rc-rwvf-8q5r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
The `size` option isn't honored after following a redirect in node-fetch
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
node-fetchnpmDescription
Impact
Node Fetch did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure.
For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.
Patches
We released patched versions for both stable and beta channels:
- For
v2: 2.6.1 - For
v3: 3.0.0-beta.9
Workarounds
None, it is strongly recommended to update as soon as possible.
For more information
If you have any questions or comments about this advisory:
- Open an issue in node-fetch
- Contact one of the core maintainers.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | node-fetch | ≥ 2.0.0&&< 2.6.1 | 2.6.1 |
| 📦npm | node-fetch | ≥ 3.0.0-beta.1&&< 3.0.0-beta.9 | 3.0.0-beta.9 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update node-fetch to 2.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w7rc-rwvf-8q5r is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-w7rc-rwvf-8q5r 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-w7rc-rwvf-8q5r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w7rc-rwvf-8q5r in your dependencies?
O3 detects GHSA-w7rc-rwvf-8q5r across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.