Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

n/a · Vulnerability

cve-program · severity unknowneuvd · severity unknownCVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS 2.0 · [email protected] · Primary 5.0 MEDIUMPublisher rating HIGHFixed by npm 2.15.1Fixed by npm 3.8.3KEV status unknown

cve-program · CVE-2016-3956

Published

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.

Read the publisher's advisory

euvd · EUVD-2018-0293

Published

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.

Read the publisher's advisory

nvd · CVE-2016-3956

Published

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.

Read the publisher's advisory

osv · GHSA-m5h6-hr3q-22h5

Published

Affected versions of the `npm` package include the bearer token of the logged in user in every request made by the CLI, even if the request is not directed towards the user's active registry. An attacker could create an HTTP server to collect tokens, and by various means including but not limited to install scripts, cause the npm CLI to make a request to that server, which would compromise the user's token. This compromised token could be used to do anything that the user could do, including publishing new packages. ## Recommendation 1. Update npm with `npm install npm@latest -g` 2. [Revoke your Tokens](https://www.npmjs.com/settings/tokens) 3. Enable [Two-Factor Authentication](https://docs.npmjs.com/getting-started/using-two-factor-authentication)

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2016-3956

Published

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain …

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.

Source published
2 Jul 2016 14:00:00 UTC
Source modified
6 Aug 2024 00:10:31 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

euvd · EUVD-2018-0293

Published

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain …

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jul 2, 2016, 2:00:00 PM

dateUpdated: Aug 6, 2024, 12:10:31 AM

Source published
Jul 2, 2016, 2:00:00 PM (timezone not stated)
Source modified
Aug 6, 2024, 12:10:31 AM (timezone not stated)
Saved here
18 Nov 2026 09:50:59 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

nvd · CVE-2016-3956

Published

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain …

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.

Additional publisher context

NVD 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

Original publisher date fields

published: 2016-07-02T14:59:19.417

lastModified: 2026-06-17T00:46:38.163

92 source CPE criteria · context only
  • cpe:2.3:a:ibm:sdk:*:*:*:*:*:nodejs:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.3:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.4:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.5:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.6:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.7:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.8:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.9:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.10:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.11:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.12:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.13:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.14:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.15:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.16:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.16-isaacs-manual:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.17:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.18:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.19:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.20:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.21:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.22:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.23:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.24:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.25:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.26:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.27:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.28:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.29:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.30:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.31:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.32:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.33:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.34:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.35:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.36:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.37:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.38:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.39:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.40:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.10.41:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.12.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.12.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.12.3:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.12.4:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.12.5:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.12.6:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.12.7:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.12.8:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:0.12.9:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.3.1:rc.1:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.3.1:rc.2:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.4.0:rc.1:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.4.0:rc.2:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.4.0:rc.3:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.4.0:rc.4:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:4.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.8.1:rc.1:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nodejs:node.js:5.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:npmjs:npm:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
2 Jul 2016 14:59:19 UTC
Source modified
17 Jun 2026 00:46:38 UTC
Saved here
24 Oct 2026 13:20:18 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Primary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS 2.0 · [email protected] · Primary · 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

osv · GHSA-m5h6-hr3q-22h5

Published

npm Token Leak in npm

Affected versions of the `npm` package include the bearer token of the logged in user in every request made by the CLI, even if the request is not directed towards the user's active registry. An attacker could create an HTTP server to collect tokens, and by various means including but not limited to install scripts, cause the npm CLI to make a request to that server, which would compromise the user's token. This compromised token could be used to do anything that the user could do, including publishing new packages. ## Recommendation 1. Update npm with `npm install npm@latest -g` 2. [Revoke your Tokens](https://www.npmjs.com/settings/tokens) 3. Enable [Two-Factor Authentication](https://docs.npmjs.com/getting-started/using-two-factor-authentication)

Source published
31 Jul 2018 22:58:35 UTC
Source modified
10 Sep 2026 03:47:01 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

Publisher rating · HIGH

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 05:53 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current