Skip to content

Tutorial · Security · Intermediate · 5 min read

Node.js October 2026 Security Update: Patch 22, 24 and 26 Safely

Node.js released security fixes on 21 October 2026 for DNS, TLS, Brotli and more. Check affected versions and follow a safe production patching checklist.

Updated 23 October 2026. The Node.js project released security updates on 21 October for its supported 22.x, 24.x and 26.x lines. The announcement covers high-severity issues involving DNS, TLS hostname checks and Brotli decoding, alongside other fixes. If your website runs on Node.js, updating application packages alone does not update the Node.js runtime. This guide shows how to identify the running version, deploy a fixed build and verify the result.

1. Which Node.js versions contain the October fixes?

  • Node.js 22.x: update to 22.23.4 or a later security-fixed build in the same supported line.
  • Node.js 24.x: update to 24.22.1 or a later security-fixed build in the same supported line.
  • Node.js 26.x: update to 26.12.1 or a later security-fixed build in the same supported line.
  • These are upstream Node.js release numbers from 21 October 2026. Distribution packages and managed platforms may deliver equivalent vendor-backed fixes differently; verify their advisories rather than relying only on a version string.
  • As of 23 October, 22.x and 24.x are LTS lines; 26.x is Current and is scheduled to become LTS on 28 October 2026. Node.js 20.x is end-of-life upstream and should not be treated as patched by this release.

2. What did the security release address?

  • CVE-2026-111497 (High): a Brotli decoder out-of-bounds write that the Node.js advisory describes as permitting remote code execution. Risk depends on whether and how your service processes affected compressed data.
  • CVE-2026-105482 (High): DNS resolution input containing a NUL character could be truncated. The fix covers 22.x, 24.x and 26.x.
  • CVE-2026-106069 (High): a TLS certificate hostname validation bypass involving hostnames that loosely resolve to an IP address; the fix covers 22.x, 24.x and 26.x.
  • CVE-2026-105483 (High): a separate TLS hostname validation issue involving fullwidth IP digits, affecting 24.x and 26.x.
  • The release also fixes medium- and low-severity issues involving HTTP keep-alive, certificate checks, random-number caches in snapshots, permission handling and other components. Consult the official advisory for line-by-line applicability.

3. Inventory every runtime, not just your laptop

Check production web servers, background workers, scheduled jobs, serverless functions, container images, CI runners and staging deployments. The command-line Node version on your workstation may not match the executable serving real traffic. Record each environment, owner, major release line, patch level and update mechanism.

Example
node --version
node -p "process.execPath"
node -p "JSON.stringify(process.versions, null, 2)"
# For containers, inspect the image and then check inside a running container:
docker ps --format 'table {{.Names}}\t{{.Image}}'
docker exec <container-name> node --version

4. Patch safely without breaking your application

  1. Take a restorable backup or snapshot and document the currently deployed artifact. Confirm that rollback will not undo unrelated database changes.
  2. Read the official Node.js advisory and your runtime provider's release notes. Stay on your existing supported major line for an urgent patch unless a major upgrade is separately tested.
  3. Update the actual Node.js binary, base image or managed runtime. Rebuild and redeploy immutable images; editing a Dockerfile or updating npm dependencies alone does not patch a running container.
  4. Reinstall dependencies in a clean build environment when appropriate, then run unit, integration and end-to-end tests. Pay special attention to native modules, TLS integrations, HTTP clients, compressed responses and startup snapshots.
  5. Deploy gradually using a staging environment, canary or rolling rollout. Restart or replace every Node.js process and worker so old binaries are not left running.
  6. Check the running version in every production replica and verify the release/build provenance. Review logs, error rates, latency, user sign-ins, payment flows and outbound API calls.
  7. Record who patched what, when, and which systems remain on unsupported or unverified runtimes. Escalate any systems that cannot be patched promptly.

5. Docker and CI/CD: common traps

For Docker, update the base image to a verified fixed release in your chosen major line, pull the new image, rebuild the application and redeploy it. Prefer digest-pinned images for reproducible releases; review and intentionally refresh the digest when a security update lands. A mutable tag alone does not guarantee every host has pulled the latest image.

Example
# Example only: select a verified, supported image variant for your app.
FROM node:24.22.1-bookworm-slim
WORKDIR /app
COPY package*.json ./
RUN npm ci --omit=dev
COPY . .
CMD ["node", "server.js"]

In CI, check the Node version used for tests and builds separately from the Node version deployed to production. npm audit checks package dependencies; it does not prove that the Node.js executable, bundled libraries or system CA store are patched. Similarly, a successful build is not evidence that every old worker has been replaced.

6. Verify the patch and monitor the rollout

  1. Read the version from the production process or running container after deployment, not just from your developer terminal.
  2. Confirm the deployment image digest or package build identifier matches the approved patched artifact.
  3. Smoke-test your critical journeys: homepage, login, forms, API requests, outbound HTTPS calls and scheduled tasks.
  4. Review error logs and metrics for new TLS failures, decompression errors, process crashes and unusual client/server errors.
  5. Watch availability and response times during rollout; investigate any regressions and follow your tested rollback procedure if necessary.
  6. Repeat the inventory across replicas, workers and regions, and schedule follow-up remediation for end-of-life Node versions.

7. What Zenith can verify

Zenith can help monitor external website availability and surface certain visible configuration or reliability findings after a deployment. It cannot remotely attest to the Node.js executable version, the presence of a vendor backport or the safety of an internal Brotli decoder. Treat a clean external website audit as one signal, not as proof that CVE-2026-111497 or the other Node.js vulnerabilities are fixed.

Official sources and release notes

  • Node.js Project — 21 October 2026 security advisory: https://nodejs.org/en/blog/vulnerability/october-2026-security-releases
  • Node.js 22.23.4 release notes: https://nodejs.org/en/blog/release/v22.23.4/
  • Node.js 24.22.1 release notes: https://nodejs.org/en/blog/release/v24.22.1/
  • Node.js 26.12.1 release notes: https://nodejs.org/en/blog/release/v26.12.1/
  • Node.js release lifecycle: https://github.com/nodejs/Release

Glossary

Node.js runtime
The Node.js executable and bundled components that run JavaScript on the server, separate from npm-installed application packages.
CVE
A publicly assigned identifier for a specific reported security vulnerability.
Brotli
A compression format used for web content and other data; Node.js includes decoding support.
LTS
Long Term Support, a Node.js release phase intended for production stability and security maintenance.
Canary deployment
A rollout that directs a small share of traffic to a new build before wider deployment.
Image digest
A content-addressed identifier for a container image, used to pin the exact artifact being deployed.