Information Exposure Vulnerability in npm CLI

npm Updated 02 Oct 2025

Summary

07/07/2020
N/A
Yes i
Medium
4.4

CVE-2020-15095: Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. Affects npm across 2 version ranges.

< 6.14.6+ds-1 < a9857b8f6869451ff058789c4631fadfde5bbcbc

Fixed in 6.14.6+ds-1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The npm CLI is a command-line interface tool used for managing JavaScript packages. It is widely used in the development community to install, publish, and manage dependencies for Node.js projects. The CLI supports various URL formats, including those with passwords. However, versions prior to 6.14.6 have a vulnerability that exposes the password value in log files and printed output.

Vulnerability Detail

This vulnerability, identified as CVE-2020-15095, allows an attacker to obtain sensitive information, specifically passwords, by exploiting the npm CLI's handling of URLs. When a URL with a password is used, the password value is not redacted and is displayed in the command-line output and any generated log files. This can lead to unauthorized access to systems or accounts if the log files are accessible to malicious actors.

How To Fix

Minimum fixed version

6.14.6+ds-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade npm

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a workaround, users can avoid using URLs with passwords in the npm CLI. Instead, it is recommended to use alternative authentication methods or remove the password from the URL if possible.

Conclusion

In conclusion, the npm CLI prior to version 6.14.6 is vulnerable to an information exposure issue that allows passwords to be exposed in log files and command-line output. It is crucial to update to the latest version to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for npm →

Share this vulnerability

FAQ

The vulnerability allows an attacker to obtain passwords from log files and command-line output, potentially leading to unauthorized access to systems or accounts.

Versions prior to 6.14.6 are affected by this vulnerability.

There are no known exploits for this vulnerability at the moment.

Yes, the CVSS score for this vulnerability is 4.4.

Related vulnerabilities

Recent vulnerabilities recorded for npm.

How To Fix

Minimum fixed version

6.14.6+ds-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade npm

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback