Repository navigation
fix: security - Node.js to 24.22.3 (Nov 2026 security release) - #255
Merged
Merged
Conversation
Bump the exact .nvmrc pin from 24.18.0 to the patched 24.x release. Co-authored-by: Jared Wray <me@jaredwray.com>
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #255 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 13 13
Lines 1723 1723
Branches 304 304
=========================================
Hits 1723 1723 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Security fix. Bump the exact Node.js runtime pin for the November 11, 2026 Node.js security releases. No application code changed. Published
enginesranges are unchanged.Pins
.nvmrcLeft unchanged:
node-versionvalues22,24, and26(floating majors, no patch, no digest).enginesranges (>=22on packages,^22.19.0 \|\| >=24.0.0at the repo root).mcr.microsoft.com/devcontainers/javascript-node:5.2.1-24-trixie(major24plus a digest). The pinned digest still matches the current MCR manifest index for that tag. No24.22.3variant of that image is published.v24.22.3is on the Node.js dist index (2026-11-10). Official Docker Hubnode:24.22.3tags are not published yet. This repository has no Node image pin, so no image tag or digest was changed.CVEs
Highest severity is HIGH. No active exploitation is reported. Patched lines are Node.js v22.23.5, v24.22.3, and v26.13.1. This repository only pins 24.x, so the pin moves to 24.22.3.
CHECK_EQin~Http2Session()), affects 24.x/26.xllhttp_execute()respondWithFile()during a pending writerespondWithFile()download is cancelledsession.altsvc()maxSessionMemoryERR_PROXY_INVALID_CONFIGhttps.Agentvia cross-policy TLS session reuseAlso includes llhttp, undici, and sqlite dependency updates in the Node.js release.
After merge
Rebuild and redeploy is required after merge (for runtime images). This library has no runtime image; the change is the local/dev
.nvmrcpin used bynvm use.No
minimumReleaseAgeExcludeentry was added.