Repository navigation
[_]: fix/pin-node-24.22.1-security-release - #423
Merged
Merged
Conversation
xabg2
approved these changes
Oct 23, 2026
|
This branch was previously deployed
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.
What
node:24-alpinetag tonode:24.22.1-alpine.Why
Node.js shipped a security release on 2026-10-21 fixing 10 CVEs, including a high-severity
remote code execution in the bundled Brotli decoder (CVE-2026-111497) and TLS hostname
validation bypasses (CVE-2026-105483, CVE-2026-106069).
Pinning the exact version makes the deployed runtime explicit and ensures future Node
updates arrive as reviewable PRs instead of depending on when the last commit happened.
References
(CVE-2026-111497) deps: brotli: cherry-pick 0ed4268a4401abcb44720963plus the TLS/DNS fixes.24.22.1-alpinetag published.