Node.js vs Eureka

Node is maintaining three lines at once — 26.x Current, 24.x 'Krypton' LTS and 22.x 'Jod' LTS — and the window is dominated by a single coordinated security release on 29 July that shipped the same eleven CVEs to all three branches simultaneously. Three of those were rated High, and three of the eleven were in the permission model itself. Feature work continues on Current at roughly a two-week minor cadence, with 24.x absorbing the backports in large batches.

Two things are visible across these releases. The crypto layer is being systematically rebuilt — OpenSSL 3, BoringSSL and legacy backends were split apart, FIPS handling for Argon2 was corrected, and key loading is moving to OpenSSL STORE loaders — which reads as preparation for supporting more than one TLS backend cleanly. Separately, the permission model has stopped being a side experiment and is now generating its own CVEs, which is what happens when a security feature starts being relied on. Observability is the third thread, with Perfetto being wired into the build and event-loop delay sampling moving per-iteration.

Expect the crypto backend split to keep producing SEMVER-MINOR changes on Current as key handling migrates to STORE loaders, and expect the next 24.x LTS drop to be another large batch backport rather than a steady drip. Given three permission-model CVEs in one train, further hardening there is the most likely source of the next security release.