Skip to content

chore: bump Node.js to the October 2026 security release (SEC-104) - #45

Closed
glebedel wants to merge 2 commits into
mainfrom
guillaume/sec-104-node-security-release
Closed

glebedel wants to merge 2 commits into
mainfrom
guillaume/sec-104-node-security-release

Conversation

@glebedel

@glebedel glebedel commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

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 lacks workflows permission.

Written for commit 3857b57. Summary will update on new commits.

View guided diff Turn on auto-fix

Patched lines: 22.23.4, 24.22.1. Refs SEC-104.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings October 21, 2026 13:48
@glebedel
glebedel requested a review from a team as a code owner October 21, 2026 13:48

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 1 file

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Requires human review: Bumps the Volta Node pin from EOL 20.18.1 to 22.23.4 for the October 2026 security fixes. Needs human sign-off because the major-version upgrade requires compatibility validation and the PR leaves CI workflow pins un-bumped, so CI may not exercise the new version.

View guided diff | Turn on auto-fix | Re-trigger cubic

@glebedel

Copy link
Copy Markdown
Contributor Author

Closing as superseded by #46, which makes the same package.json Node change and also updates the workflow pins (SEC-104).

Requested by guillaume@stackone.com in Slack.

@glebedel glebedel closed this Nov 10, 2026
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.

3 participants