[HIGH] Patch docker-compose for CVE-2026-39833, CVE-2026-46598, CVE-2026-42502, CVE-2026-39835, CVE-2026-39827, CVE-2026-25681, CVE-2026-25680 [MEDIUM] and updated patch for CVE-2026-39832

[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 docker-compose for CVE-2026-39832

  • Fixed Patch.
  • Upstream patch has been backported manually.
  • Patch matches with the upstream patch except that the test files are not included as they are not present in source code.
  • Upstream Patch Reference
    • https://github.com/golang/crypto/commit/a1ce0fee129597fdea8dfd58d71b6b607de6bdce.patch
    • https://github.com/golang/crypto/commit/e3d1254f1e7e60baa086142c46174bf6d8d0fe50.patch

• Patch docker-compose for CVE-2026-39833

  • Upstream patch has been backported manually.
  • Patch matches with the upstream patch except that the test files are not included as they are not present in source code.
  • Upstream Patch Reference: https://github.com/golang/crypto/commit/0fb843a472225645e917c84f1f9744757f0bab14.patch

• This PR also adds CVE fixes merged in 3.0-dev branch via [AutoPR- Security] Patch docker-compose for CVE-2026-46598, CVE-2026-42502, CVE-2026-39835, CVE-2026-39827, CVE-2026-25681, CVE-2026-25680 [MEDIUM] #17576

Change Log

• new file: SPECS/docker-compose/CVE-2026-25680.patch
• new file: SPECS/docker-compose/CVE-2026-25681.patch
• new file: SPECS/docker-compose/CVE-2026-39827.patch
• new file: SPECS/docker-compose/CVE-2026-39835.patch
• new file: SPECS/docker-compose/CVE-2026-42502.patch
• new file: SPECS/docker-compose/CVE-2026-46598.patch
• new file: SPECS/docker-compose/CVE-2026-39833.patch
• modified: SPECS/docker-compose/CVE-2026-39832.patch
• modified: SPECS/docker-compose/docker-compose.spec

Does this affect the toolchain?

NO

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-39832
• https://nvd.nist.gov/vuln/detail/CVE-2026-39833

Test Methodology

• Local build was successful.
• Patch applies cleanly
• License check script shows no warning.
• Installation and Uninstallation on docker image was successful.

[Kanishk-Bansal]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[v-aaditya]

Buddy Build has been triggered and it has passed. Patch applies cleanly (checked .rpm.log).

[v-aaditya]

The pipeline build has failed due to ptest failures in packages vitess and python-twisted which are unrelated to this PR.

[v-aaditya]

Re-triggered Buddy Build and it has passed. Patches apply cleanly (Checked .rpm.log).

[v-aaditya]

The PR #17576 has been cherry-picked to fix CVEs - CVE-2026-46598, CVE-2026-42502, CVE-2026-39835, CVE-2026-39827, CVE-2026-25681, CVE-2026-25680 [MEDIUM]

[CBL-Mariner-Bot]

Auto cherry-pick results:

• 3.0-dev ✅ -> Skipped

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1134729&view=results