Critical Vulnerability in npm Package: CVE-2026-0775

npm Updated 22 Oct 2026

Summary

23/01/2026
N/A
No i
High
7.0

DEBIAN-CVE-2026-0775: ... Affects npm versions 7.24.0+ds-1 – 9.2.0~ds2-2. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

npm (Node Package Manager) is a widely used package manager for JavaScript, enabling developers to install, share, and manage dependencies in their projects. It is an essential tool in the JavaScript ecosystem, facilitating the development of applications by providing access to a vast repository of packages. However, npm is susceptible to vulnerabilities, which can compromise the security of applications relying on it.

Vulnerability Detail

CVE-2026-0775 is a critical vulnerability affecting the npm package across multiple Debian ecosystems (11, 12, 13, and 14). The vulnerability originates from insufficient validation of input, which could allow an attacker to execute arbitrary code or manipulate the package in a harmful way. The ramifications of this vulnerability are severe, as it can lead to unauthorized access, data breaches, and potential system compromise. The CVSS score for this vulnerability is 7.0, indicating a high level of risk.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can restrict the use of the affected npm package in your projects until a patch is applied. This can be done by modifying your package.json file to exclude the vulnerable version.

Conclusion

CVE-2026-0775 represents a significant risk to applications using the npm package across various Debian ecosystems. It is crucial to address this vulnerability promptly by updating to the patched version of npm or implementing workarounds to mitigate risks. Utilizing tools like Vulert can further enhance your security posture by providing real-time monitoring of vulnerabilities.

See every vulnerability recorded for npm →

Share this vulnerability

FAQ

CVE-2026-0775 is a critical vulnerability in the npm package that allows for potential arbitrary code execution due to insufficient input validation.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If an immediate update is not possible, consider implementing a temporary workaround by restricting the use of the affected npm package in your projects.

The consequences include unauthorized access, data breaches, and potential system compromise, which can severely impact your application and its users.

Vulert monitors and alerts in real-time for open-source vulnerabilities in your software using just a manifest file like package-lock.json, ensuring you stay informed about potential risks.

Related vulnerabilities

Recent vulnerabilities recorded for npm.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback