How severe is GHSA-v3jv-wrf4-5845?

No CVSS score has been assigned to GHSA-v3jv-wrf4-5845 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v3jv-wrf4-5845?

GHSA-v3jv-wrf4-5845 affects the following packages: npm (npm). Ecosystems affected: npm.

How do I fix GHSA-v3jv-wrf4-5845?

Update npm to 1.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v3jv-wrf4-5845 is resolved across your whole dependency graph.

How do I detect GHSA-v3jv-wrf4-5845 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-v3jv-wrf4-5845 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-v3jv-wrf4-5845?

O3 pinpoints whether GHSA-v3jv-wrf4-5845 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-v3jv-wrf4-5845 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v3jv-wrf4-5845 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-v3jv-wrf4-5845?

GHSA-v3jv-wrf4-5845 is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v3jv-wrf4-5845 published, and has it been updated?

GHSA-v3jv-wrf4-5845 was published on September 1, 2020 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-v3jv-wrf4-5845

GHSA-v3jv-wrf4-5845 is a CWE-59 vulnerability in npm. O3 Security confirms whether GHSA-v3jv-wrf4-5845 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Local Privilege Escalation in npm

Also known asCVE-2013-4116

Published

Sep 1, 2020

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

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

npmnpm

18.6Mdownloads / week

Description

Affected versions of npm use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the npm process has permission to write to, potentially resulting in local privilege escalation.

Recommendation

Update to version 1.3.3 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`npm`	all versions	1.3.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 1.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v3jv-wrf4-5845 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-v3jv-wrf4-5845 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-v3jv-wrf4-5845. 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 `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.

O3 Security · Impact-Aware SCA

Is GHSA-v3jv-wrf4-5845 in your dependencies?

O3 detects GHSA-v3jv-wrf4-5845 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