Is CVE-2026-0775 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-0775 being exploited in the wild.

How severe is CVE-2026-0775?

High severity, with a CVSS score of 7, published 23 January 2026.

Which products and versions are affected?

npm (npm) 10.9.0, SEMVER:introduced=0,last_affected=11.8.0; npm CLI (npm) All versions through 11.8.0.

Is there a fix for CVE-2026-0775?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-0775 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-0775?

Check whether you run npm (npm) or npm CLI (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-0775: npm cli local privilege escalation via uncontrolled module search path

CVE-2026-0775 · Severity: high · CVSS 7 · Published 2026-01-23

npm cli, the JavaScript package manager, contains an insecure module loading mechanism that allows local attackers with low-privileged code execution to escalate their privileges and run arbitrary code. An attacker who gains initial access to a system can exploit this vulnerability to obtain the privileges of another user, potentially compromising the entire system or sensitive projects.

Technologies: npm (npm). Vendors: npm.

Quick answers

Is CVE-2026-0775 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-0775 being exploited in the wild.
How severe is CVE-2026-0775?: High severity, with a CVSS score of 7, published 23 January 2026.
Which products and versions are affected?: npm (npm) 10.9.0, SEMVER:introduced=0,last_affected=11.8.0; npm CLI (npm) All versions through 11.8.0.
Is there a fix for CVE-2026-0775?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-0775 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-0775?: Check whether you run npm (npm) or npm CLI (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

This vulnerability is a local privilege escalation flaw rooted in improper permission assignment (CWE-732) in npm cli's module handling. The application loads modules from unsecured filesystem locations without proper validation, enabling a local attacker to inject malicious code. The attack requires prior low-privileged code execution on the target system and does not require user interaction. An attacker can leverage this vulnerability to execute arbitrary code with elevated privileges. This issue was initially flagged as a duplicate and the advisory was withdrawn on 2026-02-06, with the vendor stating the behavior was by design; however, the underlying privilege escalation risk remains in affected versions through at least v11.8.0.

Affected products

npm npm cli All versions through 11.8.0

Identifiers

CVE-2026-0775
GHSA-3966-f6p6-2qr9

Timeline

2026-01-12: disclosed: Coordinated public release of ZDI advisory ZDI-26-043
2026-01-23: advisory: GHSA-3966-f6p6-2qr9 published
2026-02-06: other: GHSA advisory withdrawn as duplicate; vendor stated behavior was by design
2024-11-13: other: Vulnerability initially reported to vendor
2025-08-05: other: ZDI encouraged vendor reassessment

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.