[AutoPR- Security] Patch patch for CVE-2026-56289, CVE-2026-56288 [MEDIUM]

[azurelinux-security]

Auto Patch patch for CVE-2026-56289, CVE-2026-56288.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1156815&view=results

CVE-2026-56288 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1156821&view=results

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?

• Auto Patch patch for CVE-2026-56289 (MEDIUM), CVE-2026-56288 (MEDIUM).

Change Log

• CVE-2026-56289
• CVE-2026-56288

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-56289
• https://nvd.nist.gov/vuln/detail/CVE-2026-56288

Test Methodology

• Pipeline build id: Buddy Build URL

[azure-pipelines]

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

[Ratiranjan5]

The patch package version 2.7.6 falls within the affected range for both CVE-2026-56288 and CVE-2026-56289 (all versions prior to 2.8.0). After reviewing the source, I was able to verify that affected files and code are present.

• The AI-backported patches completely match with the corresponding upstream patches.

CVE-2026-56288:
Upstream patch Reference: https://cgit.git.savannah.gnu.org/cgit/patch.git/commit/?id=e6d6a4e021660679d7fc9150f981d4920f722313

CVE-2026-56289:
Upstream patch Reference: https://cgit.git.savannah.gnu.org/cgit/patch.git/commit/?id=faba04ef4f2b410257f76c1b9dc85e350929c4b9

• The spec file has been updated accordingly to apply the patches, and a changelog entry has been included.

• The toolchain and pkggen_core manifest files have been updated accordingly.

• The buddy build and local build completed successfully.

• patches apply cleanly for both CVEs (checked .rpm.log).

[Kanishk-Bansal]

Patch Analysis (CVE-2026-56289 matches upstream)
for CVE-2026-56288 core logic matches upstream, only minor backporting where buf is used instead of patchbuf
Overall LGTM

• Buddy Build 
• patch applied during the build (check rpm.log)
• patch include an upstream reference
• PR has security tag