GHSA-jmqm-f2gx-4fjv
Sensitive information exposure through logs in npm-registry-fetch
GHSA-jmqm-f2gx-4fjv is a medium vulnerability (CVSS 5.3) in npm-registry-fetch, published July 7, 2020. No source lists public exploit code. Fixed in npm-registry-fetch 4.0.5.
- Severity
- 5.3 MediumCVSS 3.1, GitHub Advisories
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
4.0.5npm-registry-fetch +2 more
Description
Affected versions of npm-registry-fetch are vulnerable to an information exposure vulnerability through log files. The cli supports URLs like <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>. The password value is not redacted and is printed to stdout and also to any generated log files.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Affected packages
| Package | Affected | Fixed |
|---|---|---|
npm-registry-fetchnpm | before 4.0.5 | 4.0.5 |
npm-registry-fetchnpm | 5.0.0 up to 8.1.1 | 8.1.1 |
npm-registry-fetchTuxCare:npm | 3.9.1-tuxcare.0 up to 3.9.1-tuxcare.1, plus listed versions 3.9.1 | 3.9.1-tuxcare.1 |
What each source reports
GitHub Advisories Score used
Sensitive information exposure through logs in npm-registry-fetch
Affected versions of npm-registry-fetch are vulnerable to an information exposure vulnerability through log files. The cli supports URLs like <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>. The password value is not redacted and is printed to stdout and also to any generated log files.
- Record
GHSA-jmqm-f2gx-4fjv- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-352
- Updated
- 2026-11-02
OSV
Sensitive information exposure through logs in npm-registry-fetch
Affected versions of npm-registry-fetch are vulnerable to an information exposure vulnerability through log files. The cli supports URLs like <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>. The password value is not redacted and is printed to stdout and also to any generated log files.
- Record
GHSA-jmqm-f2gx-4fjv- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-352
- Updated
- 2026-11-02
OSVCLSA-2026-1776299664No score
TuxCare security update for npm-registry-fetch (1 CVE)
TuxCare rebuilt npm-registry-fetch to address 1 CVE. Fixed in 3.9.1-tuxcare.1.
- Record
CLSA-2026-1776299664- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
References
github.com/npm/npm-registry-fetch/security/advisories/GHSA-jmqm-f2gx-4fjv
snyk.io/vuln/SNYK-JS-NPMREGISTRYFETCH-575432