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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m5h6-hr3q-22h5 can be triaged on real exposure rather than presence alone.

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 is the EPSS score for GHSA-m5h6-hr3q-22h5?

GHSA-m5h6-hr3q-22h5 has an EPSS (Exploit Prediction Scoring System) score of 6.7%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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 September 10, 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

Not in CISA KEV

GHSA-m5h6-hr3q-22h5 — npm

Fix: npm/npm@f67ecad

GHSA-m5h6-hr3q-22h5 is a Information Exposure vulnerability in npm. A fix is available for npm — see the affected versions and patch details below.

npm Token Leak in npm

Also known asCVE-2016-3956

Published

Jul 31, 2018

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

7Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

npmnpm

11.5Mdownloads / 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 install npm@2.15.1`
📦npm	`npm`	≥ 3.0.0&&< 3.8.3	3.8.3`npm install npm@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m5h6-hr3q-22h5 can be triaged on real exposure rather than presence alone.

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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

UbuntuHIGH

USN-4785-1Ubuntu

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 Security finds GHSA-m5h6-hr3q-22h5 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works