Upgade nodejs to version 24.20.0 - #18677
Merged
jslobodzian merged 2 commits intoSep 3, 2026
Merged
Conversation
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Author
|
Aditya Singh (v-aaditya)
marked this pull request as ready for review
September 1, 2026 13:56
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
/azp run |
|
Azure Pipelines: Successfully started running 1 pipeline(s). 1 pipeline(s) were filtered out due to trigger conditions. |
jslobodzian
approved these changes
Sep 3, 2026
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.
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-staticsubpackages, etc.) have had theirReleasetag incremented../cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json)./LICENSES-AND-NOTICES/SPECS/data/licenses.json,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)*.signatures.jsonfilessudo make go-tidy-allandsudo make go-test-coveragepassSummary
nodejsfrom version24.18.1 => 24.20.0.npmversion has been upgraded from11.16.0 => 11.19.0.nodejsexcept the 2undiciCVEs which are now fixed. Details are as follows -jinja2vendor package copies, both are still at vulnerable versions, so their patches are still required -tools/inspector_protocol/jinja2=2.10(imported by nodejs's inspector codegen viasrc/inspector/node_inspector.gypi→deps/inspector_protocol/code_generator.py) → CVE-2019-10906, CVE-2020-28493deps/v8/third_party/jinja2=3.1.2(imported by V8's inspector codegen viatools/v8_gypfiles/v8.gyp) → CVE-2024-22195, CVE-2024-34064, CVE-2025-27516undicipatches targetnpm'sbundledundiciversion6.27.0, which are fixed in this version → CVE-2026-12151, CVE-2026-9679 removed.undicito version6.27.0.Change Log
Does this affect the toolchain?
NO
Links to CVEs
NA
Test Methodology