chore: bump Node.js to the October 2026 security release (SEC-104)
What
Bumps the pinned Node.js version to the patched release from the 21 October 2026 Node.js security release.
"node": "20.18.1",ā"node": "22.23.4",
Files: package.json
Major version jump: this repo was on Node 18/20, which is end-of-life and receives no security fixes, so it moves to Node 22 (the oldest line still patched). Please check the CI run on this PR before merging.
Not in this PR yet: the Node pins in .github/workflows/ also need the same bump. The token that opened this PR has no workflows permission, so those edits follow on this branch once that is granted.
Why
The release fixes four HIGH-severity issues in 22.x and 24.x, including a Brotli decoder out-of-bounds write that permits remote code execution (CVE-2026-111497) and TLS certificate hostname-verification bypasses (CVE-2026-105483, CVE-2026-106069), plus bundled c-ares, OpenSSL, Undici and CA certificate updates. Patched versions: 22.23.4, 24.22.1, 26.12.1.
Tracked in SEC-104. Same change is going out to every stackonehq repo that pins a vulnerable Node version.
Testing
Version-only change, no application code touched. CI on this PR is the check that the new version builds.
Requested by guillaume@stackone.com in Slack.
š¤ Generated with Claude Code
Summary by cubic
Bumps the pinned Node.js version to 22.23.4, the patched release from the October 2026 security release, addressing four HIGH-severity CVEs including a Brotli decoder out-of-bounds write enabling remote code execution and two TLS certificate hostname-verification bypasses.
- Moves from Node 20 (end-of-life, no longer receives security fixes) to Node 22, the oldest line still patched, per SEC-104.
- Only updates the Volta pin in
package.json; the Node pin in.github/workflows/needs the same bump in a follow-up since the automation token lacksworkflowspermission.