[Medium] Patch nodejs18 for CVE-2025-59466

[v-aaditya]

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

Patch nodejs18 for CVE-2025-59466

• Upstream patch has been backported manually.

• Upstream changes in files src/debug_utils.cc and src/node_report.cc have not been included in the patch because the affected code is not present in our version of nodejs.

• Some part of upstream changes in file src/node_errors.cc have not been included in the patch as the affected code is not present in our version of nodejs.

• GetCurrentStackTrace function is added in src/node_errors.cc file for completeness.

• Upstream Patch Reference - https://github.com/nodejs/node/commit/d7a5c587c0.patch

Build/Dependency Information

The PR is a leaf PR which builds alone successfully.

Change Log

• modified: SPECS/nodejs/nodejs18.spec
• new file: SPECS/nodejs/CVE-2025-59466.patch

Does this affect the toolchain?

NO

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2025-59466

Test Methodology

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

[Kanishk-Bansal]

Buddy Build

[v-aaditya]

Buddy Build

Buddy Build has failed. looking into it.

[v-aaditya]

Again triggered the Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1037463&view=results

[v-aaditya]

Again triggered the Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1037463&view=results

@Kanishk-Bansal Buddy build is successful now.