[High] Upgrade reaper for CVE-2025-9288

[durgajagadeesh]

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

[High] Upgrade reaper for CVE-2025-9288
Astrolabe reference: https://brave-ocean-0baeae310.5.azurestaticapps.net/#/cve/CVE-2025-9288
Upstream patch reference: browserify/sha.js@f2a258e

Change Log

• Modified file: reaper.spec
• Modified file: reaper.signatures.json
• Modified file: reaper_build_caches.sh

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

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

Test Methodology

• Upgrade for CVE fix has been done cleanly
• 
• Local build log: reaper-3.1.1-20.cm2.src.rpm.log
• 

[durgajagadeesh]

Hi,
This PR is ready for review, built successful in my local VM.

I have removed several outdated patches after confirming that their changes are already present in the newly generated tarball.

All patches have been applied cleanly.

And the CVE-2025-9288 fix has already been included in the latest tarball generated by the reaper_build_script.sh script.

Note: I have the below reaper.signature.json changes while this got success!

And build log from the local VM:
reaper-3.1.1-20.cm2.src.rpm-10-09-2025-success_build.log

-Thank you!

[durgajagadeesh]

Hi,
I have completed the tests for reaper using the resultant rpm binary(reaper-3.1.1-20.cm2.x86_64.rpm).
Please find the reference screenshot below.

Note: Reaper web interface at http://localhost:8080 is running successfully.
-Thank you!

[Malateshk007]

@realsdx, gentle reminder for review and sign-off if all good.!

[realsdx]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[realsdx]

On a fresh azurelinux system the script fails with this:

Please include nodejs-npm as well as the dependency in the script

Also, since you have improved the script, please copy all the tar files in the current working directory instead of copying to reaper_caches

[durgajagadeesh]

On a fresh azurelinux system the script fails with this:

Please include nodejs-npm as well as the dependency in the script

Also, since you have improved the script, please copy all the tar files in the current working directory instead of copying to reaper_caches

Hi @realsdx ,
I have implemented the updates as you suggested, and the script is functioning correctly with these modifications.

If there’s anything else that needs to be updated, please let me know.
-Thank you!