Node.js vulnerabilities
Check Node.js runtimes for CVE-2026-111497 (Node2Shell) and interpret version findings, backports, and coverage gaps.
The Node.js vulnerabilities check examines discovered Node.js runtimes on Windows, Linux, and macOS for CVE-2026-111497 (Node2Shell) based on their version. It runs on the device, every 60 minutes by default. It does not perform an exploit test and is not a general Node.js vulnerability scanner.
Prerequisites
- The octoja agent is installed and connected on the device.
- The agent can read the Node.js files and relevant directories to be checked.
Steps
- Go to Devices and open the device.
- On the Checks tab, click Add Check → Node.js vulnerabilities.
- For installations outside the usual directories, add Additional paths.
- Click Add Check.
- After the first run, open the result. Review the Coverage gaps as well as the discovered installations.
To cover many devices, assign the check through a config package.
Settings
The check looks for Node.js in running processes, PATH, and common installation directories, including the user directories of version managers such as nvm, fnm, Volta, asdf, and mise. On Linux, it also uses the package manager (dpkg-query or rpm); on macOS, Homebrew.
Warning: Discovery covers the host only. Containers and runtimes bundled into applications, such as Electron or Bun, are not covered. Additional paths do not enable a full disk search either. An OK result does not prove that every Node.js copy on the device is safe.
Results
The detail view shows each installation's Path, Version, Package (if mapped), result, and reason. The overall result is the worst severity across installations and coverage gaps.
The check uses these minimum versions from the Node.js security releases of October 21, 2026:
The check evaluates NodeSource packages like upstream versions, by their version number.
For coverage gaps, check the listed paths, access permissions, and whether the package or process query is available. For installations that were not found, add targeted additional paths rather than large directory trees.
FAQ
Why does an updated Linux package stay on Warning?
Why does an updated Linux package stay on Warning?
Distributions often build Node.js against the system Brotli library and can backport the fix without raising the displayed Node.js version. The check does not verify these backports automatically. Compare the displayed package and version with your distribution vendor's security advisories for CVE-2026-111497. A warning alone does not confirm a vulnerability.
What should I do after a Node.js update?
What should I do after a Node.js update?
Restart the applications and services that use Node.js, then let the check run again. A process still running the old, since-replaced file appears as a coverage gap. Also remove old Node.js versions you no longer need, for example in version managers, or update them as well.
Why does a discovered installation have an unknown version?
Why does a discovered installation have an unknown version?
A discovered file does not always provide a version that can be evaluated. On Linux and macOS, the check runs Node.js to query its version only if the file and its parent directories are owned by root and not writable by the group or other users. For version-manager installations, it reads the bundled version file instead. Review unknown versions manually; do not loosen file permissions for this.
See also: PHP vulnerabilities · Set up alerts for a check
Was this helpful?
More in Antivirus & security
Acronis Cyber Protect AntivirusAntivirus StatusAppLocker Block EventsUser Account AuditStill need help? Ask the team