Skip to content

chore(SEC-104): bump Node to 22.23.5 / 24.22.3 / 26.13.1 (Nov 2026 security release) - #276

Merged
glebedel merged 3 commits into
mainfrom
chore/node-nov-2026-security
Nov 11, 2026
Merged

glebedel merged 3 commits into
mainfrom
chore/node-nov-2026-security

Conversation

@glebedel

@glebedel glebedel commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

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.Agent cross-policy session reuse).

Version strings only, same release line, no code change.

File Change
package.json 22.23.4 → 22.23.5
Full diff lines
    -      "version": "22.23.4",
    +      "version": "22.23.5",

Verification: 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.js runtime to 22.23.5 (November 2026 security release), fixing 16 CVEs, 7 rated High (HTTP/2 use-after-free and leaks, HTTPS use-after-free via llhttp, TLS 1.2 renegotiation servername bypass, https.Agent cross-policy session reuse).

  • Updates the devEngines.runtime pin in package.json and the matching node runtime entry (version and integrity hashes) in pnpm-lock.yaml, which pnpm requires for --frozen-lockfile installs.
  • Drops the unofficial-builds musl tarball variants for arm64 and x64 from the lockfile; the nodejs.org musl x64 variant remains.
  • No code changes. CI on this PR runs the new Node, and the next default-branch deploy should confirm node --version reports 22.23.5.

Written for commit 44ae099. Summary will update on new commits.

View guided diff Turn on auto-fix

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 glebedel self-assigned this Nov 11, 2026
s2d2-s1 and others added 2 commits November 11, 2026 17:48
pnpm records devEngines.runtime in the lockfile, so the exact Node pin bump
needs the matching runtime entry (version and integrity) to pass
--frozen-lockfile installs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>
…3.13

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>

@glebedel glebedel left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review at head 44ae099a (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 14 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).

@glebedel
glebedel merged commit 54689b1 into main Nov 11, 2026
14 checks passed
@glebedel
glebedel deleted the chore/node-nov-2026-security branch November 11, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants