Skepra / Web recovery & resilience

Node.js runtime security release: verify and rebuild.

The Node.js security release requires a runtime-to-feature-path decision before an agency agrees a rebuild for a client service.

Discuss the next maintenance decision

What Node.js published

On 11 November 2026, the Node.js project published security releases for the 22.x, 24.x and 26.x lines. The notice covers separate HTTP/2, HTTPS/TLS, SQLite, llhttp, undici and Permission Model conditions. It does not establish that every Node.js service is affected.

Map the running feature path

Record the Node.js version in the running SSR or API artifact, CI image and preview service. Then identify whether the service uses HTTP/2, TLS callbacks, client-certificate policies, respondWithFile or another path named by the primary notice. A package version alone is not an applicability decision.

Rebuild and retest

Choose the supported patched line, rebuild the artifact and verify the runtime inside that artifact. In staging, exercise the identified HTTP/2, TLS, file-serving or client-authentication flow with synthetic data. Record the old and new versions, tests, owner approval and recovery artifact.

Limits and handoff

This page does not claim an affected customer, exploitation or outage. Its practical output is a runtime-to-feature-path handoff for owners and agencies deciding whether defined maintenance work is needed.