Skip to content

[HIGH] Upgrade nodejs24 to 24.14.1 for CVE-2026-21710, CVE-2026-21637, CVE-2026-21717, CVE-2026-21713, CVE-2026-21714, CVE-2026-21712, CVE-2026-21716, CVE-2026-21715#16403

Merged
kgodara912 merged 3 commits intomicrosoft:3.0-devfrom
Kanishk-Bansal:topic_nodejs24-3.0
Apr 8, 2026

Conversation

@Ratiranjan5
Copy link
Copy Markdown
Contributor

@Ratiranjan5 Ratiranjan5 commented Apr 1, 2026

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

What does the PR accomplish, why was it needed?

Change Log
  • modified: SPECS/nodejs24/nodejs24.signatures.json
  • modified: SPECS/nodejs24/nodejs24.spec
  • modified: cgmanifest.json
Does this affect the toolchain?

NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology
  • Pipeline build id: xxxx

@Ratiranjan5
Copy link
Copy Markdown
Contributor Author

This PR has been kept in draft status as the BB results still need to be verified, since the build could not be completed on the local VM due to memory constraints.

@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels Apr 1, 2026
@Kanishk-Bansal
Copy link
Copy Markdown
Contributor

Buddy Build

@Kanishk-Bansal Kanishk-Bansal marked this pull request as ready for review April 1, 2026 17:47
@Kanishk-Bansal Kanishk-Bansal requested a review from a team as a code owner April 1, 2026 17:47
Copy link
Copy Markdown
Contributor

@Kanishk-Bansal Kanishk-Bansal left a comment

Choose a reason for hiding this comment

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

nodejs on v24 is on LTS and stable release, 24.14.1 is a security release with CVE-2026-21710, CVE-2026-21637, CVE-2026-21717, CVE-2026-21713, CVE-2026-21714, CVE-2026-21712, CVE-2026-21716, CVE-2026-21715

Copy link
Copy Markdown
Contributor

@Kanishk-Bansal Kanishk-Bansal left a comment

Choose a reason for hiding this comment

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

Why have you removed these patches? like CVE-2019-10906
Are these covered in this release?

@Ratiranjan5
Copy link
Copy Markdown
Contributor Author

Ratiranjan5 commented Apr 2, 2026

Why have you removed these patches? like CVE-2019-10906 Are these covered in this release?

Updated the spec file. Dropped only CVE-2025-69418.patch since the fix is already present upstream source in nodejs24-24.14.1.

Copy link
Copy Markdown
Contributor

@Kanishk-Bansal Kanishk-Bansal left a comment

Choose a reason for hiding this comment

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

remove the spec file from the folder as well,

@Kanishk-Bansal
Copy link
Copy Markdown
Contributor

Buddy Build

@Kanishk-Bansal Kanishk-Bansal self-requested a review April 2, 2026 09:51
Copy link
Copy Markdown
Contributor

@Kanishk-Bansal Kanishk-Bansal left a comment

Choose a reason for hiding this comment

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

Taking this release as this contains only bug and security fixes as nodejs24 is on LTS.

@Kanishk-Bansal
Copy link
Copy Markdown
Contributor

/azurepipelines run

@Kanishk-Bansal Kanishk-Bansal added the ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review label Apr 2, 2026
@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@Kanishk-Bansal Kanishk-Bansal changed the title Upgrade nodejs24 to 24.14.1 [HIGH] Upgrade nodejs24 to 24.14.1 for CVE-2026-21710, CVE-2026-21637, CVE-2026-21717, CVE-2026-21713, CVE-2026-21714, CVE-2026-21712, CVE-2026-21716, CVE-2026-21715 Apr 2, 2026
Copy link
Copy Markdown
Contributor

@kgodara912 kgodara912 left a comment

Choose a reason for hiding this comment

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

Minor version bump of nodejs24 package. The upgrade belongs to same LTS release series and is highly recommended to fixing CVEs. Buddy build is successful. LGTM.

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 AutoPR-Security CVE-fixed-by-upgrade CVE fixed by package upgrade Packaging ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants