How severe is GHSA-v45m-2wcp-gg98?

No CVSS score has been assigned to GHSA-v45m-2wcp-gg98 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v45m-2wcp-gg98?

GHSA-v45m-2wcp-gg98 affects the following packages: bin-links (npm). Ecosystems affected: npm.

How do I fix GHSA-v45m-2wcp-gg98?

Update bin-links to 1.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v45m-2wcp-gg98 is resolved across your whole dependency graph.

How do I detect GHSA-v45m-2wcp-gg98 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bin-links, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-v45m-2wcp-gg98 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.

Is GHSA-v45m-2wcp-gg98 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v45m-2wcp-gg98 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.

When was GHSA-v45m-2wcp-gg98 published, and has it been updated?

GHSA-v45m-2wcp-gg98 was published on September 4, 2020 and was last updated on August 31, 2020. 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

Global node_modules Binary Overwrite in bin-linksGHSA-v45m-2wcp-gg98

GHSA-v45m-2wcp-gg98 is a security vulnerability in bin-links. A fix is available for bin-links — see the affected versions and patch details below.

Published

Sep 4, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg 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.

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

bin-linksnpm

7.7Mdownloads / week

Description

Versions of bin-links prior to 1.1.6 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent globally-installed binaries to be overwritten by other package installs. For example, if a package was installed globally and created a serve binary, any subsequent installs of packages that also create a serve binary would overwrite the first binary. This behavior is still allowed in local installations.

Recommendation

Upgrade to version 1.1.6 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`bin-links`	all versions	1.1.6`npm install bin-links@1.1.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bin-links, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bin-links to 1.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v45m-2wcp-gg98 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.

Frequently Asked Questions

Versions of `bin-links` prior to 1.1.6 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent globally-installed binaries to be overwritten by other package installs. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This behavior is still allowed in local installations. ## Recommendation Upgrade to version 1.1.6 or later.

O3 Security · Impact-Aware SCA

Is GHSA-v45m-2wcp-gg98 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works