Skip to content

Node.js: October 2026 security fixes

Checked on October 23, 2026. Node.js released security updates for branches 22, 24 and 26 on October 21. The highest severity is high. See the official security announcement for details.

Fixed versions

Node.js branch Minimum fixed release
22.x 22.23.4
24.x 24.22.1
26.x 26.12.1

Use this release or a later release in the same branch. For an older unsupported branch, plan a move to a supported version and verify application compatibility.

What the update addresses

Fixes include CVE-2026-111497 in the Brotli decoder, which can allow remote code execution, and DNS and TLS certificate validation issues. Individual issues affect different branches; the Node.js announcement above lists all CVEs and affected branches.

Check the runtime actually used

In the terminal or over SSH, run as the project's Linux user:

command -v node
node --version
node -p 'process.execPath'

Compare the result with commands in project processes and deployment. If a command uses an absolute Node.js path, check that file with --version. The terminal's default node may belong to a different installation than the application. Repeat for each runtime in use, including containers and build environments.

Updating in the cloud

First compare the Node.js service inventory against the fixed versions above. The cloud only displays critical findings with a known fix; this high-severity announcement may therefore show no security update icon. See security updates for details.

If the interface does not offer an update for an installed managed branch, contact support with the server, branch and detected version. Do not uninstall a runtime in use simply to make installation available again. Consider other projects on the server before changing the default branch.

Manually installed Node.js

Update through the tool managing that installation. For Node.js installed as an Ubuntu system APT package, first check the available fix:

sudo apt-get update
apt-cache policy nodejs

Check the package origin and Candidate version. If it matches a fixed release in the current branch or the vendor confirms a backported fix, upgrade and review the proposed changes before confirming:

sudo apt-get install --only-upgrade nodejs

APT does not update runtimes managed by the cloud, a user version manager or a container. For those installations, use the corresponding manager or rebuild and deploy the container with patched Node.js. Updating npm or running npm audit fix does not replace the runtime fix.

Restart and verify

After updating, restart all affected applications and workers through their process manager. Replacing the binary does not refresh an existing process. If a command pins a path to an old release, update it and apply the configuration before restarting.

Check the correct binary's version again, process status, logs and application functionality. Application restarts may briefly interrupt availability; rebooting the entire VM is not a routine Node.js update step.