Check Node.js 24.18.0 LTS Before Your Next Runtime Upgrade

Node.js 24.18.0 LTS is now the latest Krypton LTS release. Confidence level: confirmed. The release is not a rewrite of the platform, but it includes enough runtime, dependency, crypto, and HTTP changes to justify a normal staging pass before teams update production images.

Image: Official Node.js release preview image.

What changed

The Node.js project published Node.js 24.18.0 on June 23, 2026 as an LTS release in the Krypton line. The release notes list changes across crypto, HTTP, dependencies, tests, and tooling.

For production teams, the notable items are practical rather than flashy: root certificates move to NSS 3.123.1, Web Crypto gains TurboSHAKE and KangarooTwelve algorithms, npm is upgraded, SQLite is updated, and HTTP avoids stream listeners on idle agent sockets.

Node.js 26.4.0 is also available as the latest Current release, but 24.18.0 is the safer default check for services that standardize on LTS.

Why this is early

This is early in the operational sense: the release is official, but many container bases, build images, CI templates, and platform runtimes will lag behind the upstream release page. Node's GitHub releases mirror confirms the tag, while the Node.js release schedule and endoflife.date help place v24 in its LTS window.

The main risk is not missing a headline feature. It is silently updating runtime dependencies in a service that relies on TLS trust stores, Web Crypto behavior, SQLite bindings, npm lockfile behavior, or HTTP agent edge cases.

Key takeaways

• Node.js 24.18.0 is the latest LTS release in the Krypton line.
• The release updates root certificates, npm, SQLite, and Web Crypto support.
• Node.js 26.4.0 is newer, but it is the Current line, not the LTS default.
• Services with TLS, crypto, SQLite, or HTTP connection-pooling sensitivity should stage first.
• Teams still on unsupported lines should use the release schedule before planning upgrades.

Availability and access

Node.js 24.18.0 is available from the official Node.js release page and GitHub release feed. The Node.js release schedule lists v24 as Krypton LTS, while endoflife.date tracks v24 as supported with security support running beyond the active LTS phase.

For Docker, CI, PaaS, and serverless environments, check the exact image tag or runtime selector instead of assuming the platform has already moved. Many managed environments intentionally trail upstream runtime releases.

Practical LinkLoot angle

Use this release as a staging checklist, not an emergency migration. Update one service image, run TLS-heavy integration tests, check package-manager output, and compare HTTP client metrics before rolling the runtime across every app.

If your team runs automation or AI-assisted deployment workflows, pin the runtime version in those jobs as well. The LinkLoot guide to AI workflow automation is a useful reminder to treat automation runners as production dependencies, not disposable scripts.

What to verify before you act

• Confirm whether your base image, CI runner, or PaaS runtime offers Node.js 24.18.0.
• Run certificate-sensitive integrations against the updated NSS root store.
• Check npm output and lockfile behavior in CI before merging runtime bumps.
• Test SQLite-dependent code paths if your service uses the bundled dependency.
• Keep Node.js 26.4.0 separate unless your policy allows Current-line runtimes.

Source check

Confirmed by:

• Node.js release notes confirm Node.js 24.18.0 LTS and list the runtime, dependency, crypto, HTTP, tooling, and test changes.
• Node.js GitHub releases confirm the v24.18.0 tag and the nearby v26.4.0 Current release.
• Node.js release schedule confirms the v24 Krypton LTS status.

Early signal / context:

• endoflife.date provides lifecycle context for comparing v24 LTS, v26 Current, and unsupported older lines.
• LinkLoot will treat future Node.js security releases or LTS lifecycle changes as stronger update triggers than routine maintenance releases.