Security news

Node.js security update: check the runtime behind your app

Vibe App Scanner ·

If your deployed app runs on Node.js 22.x, 24.x or 26.x, check that the runtime serving it contains the November 11 security fixes. The published security releases are 22.23.5, 24.22.3 and 26.13.1, respectively. Use the relevant release or a later supported release that includes the fixes. Official security advisory.

For Next.js builders, this is a separate task from updating the framework: Next.js documents Node.js as its default server runtime. Record both the app's dependency version and its serving runtime. Next.js runtime documentation.

Start by identifying who controls that runtime:

How your app runsYour next step
Your team controls a Node.js server or containerSelect the patched release on the supported line, test the artifact and replace the running instances
A managed platform controls the runtimeObtain the provider's fixed-release mapping and the action required for your existing deployment
You are unsure, or only know the frontend/framework versionAsk the maintainer to identify the process serving requests and any separately deployed APIs or workers

Do that inventory before treating a repository change as completion. The useful outcome is evidence that the chosen fix reached the serving process, plus a separate review of any exposed secrets or affected trust policies. The checks below are an editorial plan; VAS has not tested your deployment or reproduced an exploit.

Choose the fix for the line you already operate

The project labels each of these a November 11 security release:

Your supported runtime linePublished security releasePrimary release details
22.x22.23.5Node.js 22.23.5
24.x24.22.3Node.js 24.22.3
26.x26.13.1Node.js 26.13.1

Use the applicable release or a later supported release that contains these fixes. If your host or operating-system distributor supplies backports, obtain its mapping to the advisory. Do not reject or approve a distributor package by comparing its displayed version string alone.

Preserve an intentional release line while testing compatibility. Moving from 22.x to 26.x is a separate migration decision; a higher major version is not required just to select the published patch for 22.x. For production, Node.js recommends Active LTS or Maintenance LTS releases. Unsupported runtimes need a tested migration plan rather than an assumption that omission from the supported-release table means safety. Release policy.

Match the vulnerabilities to the actual deployment

The advisory now describes HTTP/2, HTTPS, TLS, proxy-error disclosure and other issues. Their conditions differ. Use it as a set of configuration questions, rather than assuming that every Node.js app exposes every path. This guide highlights examples and is not an exhaustive assessment of all the release’s fixes.

One high-severity issue, CVE-2026-123864, can disclose memory from other connections in affected Node.js HTTPS handling. The project describes handler prerequisites involving response-header flushing before the body ends and later response writes; reading the leaked memory also requires a route that echoes or stores a request body. It explicitly excludes cleartext node:http from this particular issue. HTTPS issue and prerequisites.

That makes the TLS boundary a useful question for your engineer: does Node.js itself handle HTTPS, or does an upstream service terminate TLS and forward cleartext HTTP? Answer it from your deployment configuration. An HTTPS address in the browser does not answer which process performs TLS. An upstream terminator also does not establish exemption from the other issues in this release.

Several HTTP/2 issues concern session teardown, response buffers or file-serving operations. The project also describes TLS client-certificate authorization bypasses, including CVE-2026-123872 involving different certificate policies per hostname. These are not a claim that ordinary password login is universally bypassed. Per-issue scope.

Ask the app owner to classify these paths:

Deployment questionEvidence to retain
Does a Node.js process receive HTTP/2 directly?Server configuration and the boundary between proxy and application
Does the app use custom TLS callbacks or hostname-specific client certificates?Relevant configuration and the intended authorization policy
Does it use custom outbound HTTPS agents and CA policies?The configured client, trust policy and owning service
Does it use authenticated outbound proxies?Configuration ownership and where errors can be recorded, without copying credentials

The advisory describes an HTTPS Agent session-reuse issue, CVE-2026-123877, and proxy credentials appearing in certain error messages, CVE-2026-123871. Review those paths even if Node.js does not terminate incoming browser TLS. Outbound and proxy issues.

If an AI coding assistant helps locate configuration, ask for file names, relevant option names and deployment ownership. Review its conclusions. Keep tokens, private keys, complete proxy URLs and customer records out of prompts and tickets.

Record the running version before changing configuration

In a development terminal or an authorized service shell, these commands inspect the executable selected in that environment:

node --version
node -p 'process.versions.node'

Node.js documents process.versions.node as the version string without the leading v. These commands do not install a patch. Process version documentation.

A laptop result describes your laptop. A build-shell result describes the build environment. Obtain the serving runtime through private operational information or a controlled observation in the application’s own execution environment. Do not add a public version-reporting endpoint for this task.

Make a separate inventory row for the web application, standalone API, worker and any retained preview or recovery deployment. Record the runtime, deployment identifier, owner and unresolved questions. A worker may share a repository with the website while running in a different artifact or service.

For serverless or other managed deployments, ask the provider which runtime release serves your functions and what action applies to an existing deployment. A provider’s support for a major line does not by itself establish that your particular deployed function contains today’s fixes.

Change the setting that controls the deployed runtime

Find the authoritative version selector before editing a repository file. On Render, the documented precedence is the service’s NODE_VERSION, then .node-version, then .nvmrc, then package.json’s engines field. Render also warns about unbounded ranges resolving to a later major version. Those are Render-specific rules. Render’s Node.js version selection.

If a higher-priority service setting selects the runtime, changing .nvmrc alone will not close the task. Inspect only the relevant setting; do not export the service’s entire environment. For another host, use that provider’s current instructions instead of copying Render’s precedence.

For a container deployment, identify the runtime in the built artifact and the image that running instances use. Plan the rebuild and replacement of those instances. Updating an npm dependency, changing a lockfile or editing a Dockerfile is incomplete evidence until the intended runtime reaches the serving process.

Keep the deployment procedure reversible, with a security-aware recovery plan. Before selecting a fallback artifact, check whether it restores a runtime that lacks the released fixes. Do not use a rollback as an unrecorded exception to the update.

Verify the replacement with harmless application checks

Use representative staging accounts and synthetic data first. The following is an editorial acceptance plan, not an exploit reproduction or a test VAS has performed:

  1. Record the selected patched runtime and artifact identifier.
  2. Run an ordinary sign-in and read a synthetic private page with the intended test account.
  3. Exercise one authorized API operation and, if applicable, a normal file upload or download.
  4. Run a harmless background job in each separately deployed worker.
  5. After the authorized rollout, observe the serving runtime again and record the production deployment identifier.
  6. Check remaining instances and retained environments individually; leave missing evidence open.

For applications with mutual TLS, include an authorized staging check of the intended client-certificate boundary. Do not weaken certificate verification to get a compatibility check to pass. For custom HTTPS agents, verify the intended outbound trust policy using controlled test services.

Avoid crash payloads, memory-disclosure probes and real customer traffic as a validation method. Successful normal workflows support compatibility, while the runtime and artifact records support deployment of the chosen fix. Neither proves that every advisory was reachable before the update or that no earlier compromise occurred.

Keep exposure review separate from patch deployment

The proxy-error issue warrants a specific historical question: could credential-bearing errors have reached logs or error-reporting systems? Have an authorized owner review access and retention without copying secret values into the incident record. If exposure is confirmed, follow the credential issuer’s response process as well as fixing the runtime. Proxy-error disclosure description.

Similarly, a memory-disclosure advisory is not proof that your TLS keys were stolen. Record the deployment conditions, available evidence and gaps. Assign any necessary incident investigation separately from the patch task rather than declaring either compromise or absence of compromise from a version check.

Close the update with one record per service: previous runtime, chosen fixed-release reference, new observed runtime, artifact and deployment identifiers, verification time, compatibility results and remaining work. Keep the owner of each exception visible.

The official releases are available; provider rollout timing, distributor mappings and your application’s exposure still require app-specific evidence. Reopen the Node.js security advisory and relevant release page before acting or publishing. Sources were checked November 16. This guide does not report independent exploitation or completed remediation of your app.