Repository navigation
chore(SEC-104): bump Node to 22.23.5 / 24.22.3 / 26.13.1 (Nov 2026 security release) - #8
Merged
Merged
Conversation
22.23.5 / 24.22.3 / 26.13.1 fix 16 CVEs (7 High) in HTTP/2, HTTPS (llhttp), TLS and https.Agent. https://nodejs.org/en/blog/vulnerability/november-2026-security-releases Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
glebedel
commented
Nov 11, 2026
glebedel
left a comment
Contributor
Author
There was a problem hiding this comment.
Review at head dd196f1b (Node Nov 2026 security release, SEC-104).
- Correctness (Codex pass over all 68 bump PRs): OK. Pins in this repo agree; no stale 22.23.4 / 24.22.1-2 / 26.12-13.0 left in the diff.
- Security (Codex security-only pass): no findings. Lockfile node runtime URLs and hashes match the official SHASUMS256; no workflow permission or action-pin changes.
- CI: all 7 checks green on this head.
- Open review threads: 0.
Ready to merge from my side. GitHub approval still has to come from a person: s2d2 cannot approve PRs, and in this repo s2d2 acts with the same identity that opened the PR.
Requested by guillaume@stackone.com in Slack (#C05LDDNTJKV thread 1793813777.685889).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the pinned Node version to the November 2026 Node.js security release: 22.23.5 / 24.22.3 / 26.13.1. The release fixes 16 CVEs, 7 rated High (HTTP/2 use-after-free and leaks, HTTPS use-after-free via llhttp, TLS 1.2 renegotiation servername bypass of client-cert auth,
https.Agentcross-policy session reuse).Version strings only, same release line, no code change.
.nvmrcFull diff lines
-22.23.4 +22.23.5Verification: CI on this PR runs on the new Node (the workflows read the pinned version). No runtime demo: a patch bump inside the same release line with no code change.
Post-merge validation: next deploy/CI run on the default branch reports the new
node --version; no new error signatures in the following deploy window.Requested by guillaume@stackone.com in Slack (#C05LDDNTJKV thread 1793813777.685889).
🤖 Generated with Claude Code
Summary by cubic
Bumps the pinned Node version in
.nvmrcfrom 22.23.4 to 22.23.5 as part of the November 2026 Node.js security release. The patch fixes 16 CVEs, 7 rated High, covering HTTP/2 use-after-free, HTTPS use-after-free via llhttp, and TLS renegotiation issues. Version-only change on the same release line; no code changes.Written for commit dd196f1. Summary will update on new commits.