CVE-2022-0235 | Exposure of Sensitive Information to an Unauthorized Actor in node-fetch/node-fetch

Exp

node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor

Published: 2022-01-16 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-0235 is rated High Exploit Risk (66.4/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.65%). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +1.36% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-0235

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-0235

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.29% 1.65% +1.36%
2 2026-04-14 0.53% 0.29% -0.24%
3 2026-03-26 — 0.53% —

Full EPSS history (42 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-0235

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.7 [email protected]
8.8 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
5.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 4.9 [email protected]

Weakness enumeration for CVE-2022-0235

GitHub Security Advisory for CVE-2022-0235

GHSA-r683-j2x4-v87g · Severity: high · Ecosystem: npm — node-fetch forwards secure headers to untrusted sites

OS Trackers for CVE-2022-0235

vendor priority summary link
debian not yet assigned CVE-2022-0235 not yet assigned priority: Debian including 1 source packages (node-fetch), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-0235
redhat medium — https://access.redhat.com/security/cve/CVE-2022-0235
suse medium CVE-2022-0235 severity moderate: SUSE including 36 source package names (12-15.7:nodejs12-12.22.12-150200.4.32.1, 12-15.7:npm12-12.22.12-150200.4.32.1, …), 272 product×package rows across 30 product lines (Container bci/nodejs, SUSE CaaS Platform 4.0, … (30 product lines)): Fixed 272. https://www.suse.com/security/cve/CVE-2022-0235/
ubuntu medium CVE-2022-0235 medium priority: Ubuntu including 1 source packages (node-fetch), 9 status rows across 9 suites (bionic, focal, impish, jammy, kinetic, lunar, trusty, upstream, xenial): ignored 3, not-affected 3, released 3. https://ubuntu.com/security/CVE-2022-0235

Affected software / configurations for CVE-2022-0235

Vendor Product Version Raw CPE
node-fetch_project node-fetch < 2.6.7 cpe:2.3:a:node-fetch_project:node-fetch:*:*:*:*:*:node.js:*:*
node-fetch_project node-fetch >= 3.0.0, < 3.1.1 cpe:2.3:a:node-fetch_project:node-fetch:*:*:*:*:*:node.js:*:*
siemens sinec_ins < 1.0 cpe:2.3:a:siemens:sinec_ins:*:*:*:*:*:*:*:*
siemens sinec_ins 1.0 cpe:2.3:a:siemens:sinec_ins:1.0:-:*:*:*:*:*:*
siemens sinec_ins 1.0 cpe:2.3:a:siemens:sinec_ins:1.0:sp1:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2022-0235

cvelogic Threat Intelligence