CVE-2022-0235
HIGHCVE-2022-0235 is a high-severity (CVSS 8.8) Information Exposure vulnerability in node-fetch. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2022-0235 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Exposure of Sensitive Information to an Unauthorized Actor in node-fetch/node-fetch
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
node-fetchnpmDescription
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | node-fetch | ≥ 3.0.0&&< 3.1.1 | 3.1.1 |
| 📦npm | node-fetch | all versions | 2.6.7 |
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 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 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0235 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 CVE-2022-0235 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 CVE-2022-0235. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-0235 in your dependencies?
O3 detects CVE-2022-0235 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.