Understand threats and change
Node.js security update: fixed versions 22.23.4, 24.22.1 and 26.12.1
What should I ask my IT team or supplier to do?
Update every supported Node.js installation to 22.23.4, 24.22.1 or 26.12.1, matching its major release line.
Node.js is behind-the-scenes software used by many websites, online shops and apps. This flaw could let an attacker run their own code on the computer that powers an affected service. Tell your IT team, web developer, software supplier or hosting company about the update. Ask them to check any websites, apps or services they manage, install the matching fix, and confirm when it is done. The fixed versions are 22.23.4 for Node.js 22, 24.22.1 for Node.js 24, and 26.12.1 for Node.js 26. If they find Node.js 20 or older, ask for a plan to upgrade.
Node.js released security updates on 21 October 2026 for its 22.x, 24.x and 26.x lines. Apply the patch matching each line: 22.23.4, 24.22.1 or 26.12.1. The release fixes four high severity vulnerabilities, including a flaw in the Brotli decoder that the project says permits remote code execution (RCE) 1Reference 1: Wednesday, October 21, 2026 Security Releases. RCE means an attacker may be able to make code run on an affected system. The notice does not describe the exploit conditions or say whether attacks are under way. Patch every live installation instead of trying to infer exposure from the short notice.
Think of each Node installation as a separate copy of a door lock: changing the one on a developer’s laptop does not change the lock on the production service. A laptop, build runner, container image, production server and scheduled job can each run a different Node.js binary. Check the environment that actually serves the application.
Match the patch to the runtime
- Node.js 22: 22.23.4
- Node.js 24: 24.22.1
- Node.js 26: 26.12.1
The node --version command reports the version in the environment where it runs. Check from inside each production container or host, or ask its owner for the deployed runtime version. Updating a project’s packages does not necessarily update the Node.js binary supplied by a container or hosting provider.
What the release fixes
The Brotli flaw is CVE-2026-111497. The other three high severity issues affect DNS handling and TLS certificate hostname checks. One TLS issue involves IP addresses written with fullwidth digits and affects Node 24 and 26; another involves hostnames that loosely resolve to an IP address, and affects all three lines. Node also fixed DNS handling for names containing a NUL character. The security notice lists additional medium and low severity issues, so deploy the complete release 1Reference 1: Wednesday, October 21, 2026 Security Releases.
The update also changes certificates trusted by Node.js. The advisory lists a ca-cert update for all three lines. Mozilla reported that private keys associated with eight eMudhra intermediate certificates had been compromised and could be used to issue fraudulent HTTPS certificates 2Reference 2: Protecting Firefox users following the compromise of eMudhra intermediate certificates. Node 24.22.1’s release notes confirm an update to its root certificate list, to NSS 3.131.1 3Reference 3: Node.js 24.22.1 (LTS). Ask a hosting provider to confirm that its managed runtime includes the certificate update as well as the security fixes.
Close the gap in production
List the websites, APIs, background jobs and build images that use Node.js. Record the owner and exact version for each. Upgrade supported installations to the matching patch, rebuild and redeploy containers, then verify the version inside the running service and test important customer tasks such as sign-in or payment.
If a system still runs Node 20 or an older line, do not wait for a patch number that will not arrive from the Node.js project. End-of-life versions no longer receive project security updates; Node 20 reached end of life on 24 March 2026 1Reference 1: Wednesday, October 21, 2026 Security Releases 4Reference 4: End-Of-Life (EOL). Plan a move to a maintained release and ask the provider for its supported upgrade path.
If time is limited, start with the service whose failure would stop sales or essential work. Our small business cyber security guide shows how to trace that work to the systems it depends on.