node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
Exact source revision recorded 24 Oct 2026 19:17:37 UTC. It does not establish the source's current position. Latest evidence.
nvd · CVE-2022-0235
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-200 · CWE-601
Original publisher date fields
published: 2022-01-16T17:15:07.870
lastModified: 2026-10-07T18:17:11.073
5 source CPE criteria · context only
- cpe:2.3:a:node-fetch_project:node-fetch:*:*:*:*:*:node.js:*:*
- cpe:2.3:a:siemens:sinec_ins:*:*:*:*:*:*:*:*
- cpe:2.3:a:siemens:sinec_ins:1.0:-:*:*:*:*:*:*
- cpe:2.3:a:siemens:sinec_ins:1.0:sp1:*:*:*:*:*:*
- cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON