Skip to content

Upgade nodejs to version 24.20.0 - #18677

Merged
jslobodzian merged 2 commits into
microsoft:3.0-devfrom
Kanishk-Bansal:topic-upgrade/nodejs/3.0/v24.20
Sep 3, 2026
Merged

Upgade nodejs to version 24.20.0#18677
jslobodzian merged 2 commits into
microsoft:3.0-devfrom
Kanishk-Bansal:topic-upgrade/nodejs/3.0/v24.20

Conversation

@v-aaditya

@v-aaditya Aditya Singh (v-aaditya) commented Sep 1, 2026

Copy link
Copy Markdown
Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary
  • Upgrade nodejs from version 24.18.1 => 24.20.0.
  • Bundled npm version has been upgraded from 11.16.0 => 11.19.0.
  • Most of the existing CVE patches are retained as they affect the upgraded version of nodejs except the 2 undici CVEs which are now fixed. Details are as follows -
    • The build uses two separate jinja2 vendor 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 via src/inspector/node_inspector.gypideps/inspector_protocol/code_generator.py) → CVE-2019-10906, CVE-2020-28493
      • deps/v8/third_party/jinja2 = 3.1.2 (imported by V8's inspector codegen via tools/v8_gypfiles/v8.gyp) → CVE-2024-22195, CVE-2024-34064, CVE-2025-27516
    • The two undici patches target npm's bundled undici version 6.27.0, which are fixed in this version → CVE-2026-12151, CVE-2026-9679 removed.
  • Few patches are updated as the offset has changed for them.
  • This upgrade also updates npm dependency: undici to version 6.27.0.
  • Release log - https://github.com/nodejs/node/releases/tag/v24.20.0
Change Log
  • deleted: SPECS/nodejs/CVE-2026-12151.patch
  • deleted: SPECS/nodejs/CVE-2026-9679.patch
  • modified: SPECS/nodejs/CVE-2026-15157.patch
  • modified: SPECS/nodejs/disable-tlsv1-tlsv1-1.patch
  • modified: SPECS/nodejs/nodejs.signatures.json
  • modified: SPECS/nodejs/nodejs.spec
  • modified: cgmanifest.json
Does this affect the toolchain?

NO

Links to CVEs

NA

Test Methodology
  • Local build could not be triggered due to resource limitation.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@microsoft-github-policy-service microsoft-github-policy-service Bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels Sep 1, 2026
@v-aaditya

Aditya Singh (v-aaditya) commented Sep 1, 2026

Copy link
Copy Markdown
Author
  • Updated Tar ball uploaded on blob store.
  • Buddy Build has been triggered and it has passed.
  • All the retained patches apply cleanly. (Checked .rpm.log)
  • Ptest has passed. (Checked .rpm.test.log)

@v-aaditya
Aditya Singh (v-aaditya) marked this pull request as ready for review September 1, 2026 13:56
@v-aaditya
Aditya Singh (v-aaditya) requested a review from a team as a code owner September 1, 2026 13:56
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@kgodara912

Copy link
Copy Markdown

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.

@jslobodzian
jslobodzian merged commit 549cd50 into microsoft:3.0-dev Sep 3, 2026
31 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0-dev PRs Destined for AzureLinux 3.0 Packaging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants