How severe is GHSA-m5h6-hr3q-22h5?

No CVSS score has been assigned to GHSA-m5h6-hr3q-22h5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m5h6-hr3q-22h5?

GHSA-m5h6-hr3q-22h5 affects the following packages: npm (npm), npm (npm). Ecosystems affected: npm.

How do I fix GHSA-m5h6-hr3q-22h5?

Update npm to 2.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m5h6-hr3q-22h5 is resolved across your whole dependency graph.

How do I detect GHSA-m5h6-hr3q-22h5 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for npm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m5h6-hr3q-22h5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-m5h6-hr3q-22h5?

O3 pinpoints whether GHSA-m5h6-hr3q-22h5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m5h6-hr3q-22h5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m5h6-hr3q-22h5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-m5h6-hr3q-22h5?

GHSA-m5h6-hr3q-22h5 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m5h6-hr3q-22h5 published, and has it been updated?

GHSA-m5h6-hr3q-22h5 was published on July 31, 2018 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-m5h6-hr3q-22h5

GHSA-m5h6-hr3q-22h5 is a Information Exposure vulnerability in npm. O3 Security confirms whether GHSA-m5h6-hr3q-22h5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

npm Token Leak in npm

Also known asCVE-2016-3956

Published

Jul 31, 2018

Updated

Feb 4, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

npmnpm

18.6Mdownloads / week

Description

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

Update npm with npm install npm@latest -g
Revoke your Tokens
Enable Two-Factor Authentication

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`npm`	all versions	2.15.1
📦npm	`npm`	≥ 3.0.0&&< 3.8.3	3.8.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for npm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update npm to 2.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m5h6-hr3q-22h5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m5h6-hr3q-22h5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m5h6-hr3q-22h5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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. [R

O3 Security · Impact-Aware SCA

Is GHSA-m5h6-hr3q-22h5 in your dependencies?

O3 detects GHSA-m5h6-hr3q-22h5 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works