[AutoPR- Security] Patch libgit2 for CVE-2026-53587, CVE-2026-53586, CVE-2026-53585, CVE-2026-53584, CVE-2026-53583 [HIGH]

[Azure Linux Security Servicing Account (azurelinux-security)]

Auto Patch libgit2 for CVE-2026-53587, CVE-2026-53586, CVE-2026-53585, CVE-2026-53584, CVE-2026-53583.

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

CVE-2026-53585 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1187180&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 libgit2 for CVE-2026-53587 (HIGH), CVE-2026-53586 (MEDIUM), CVE-2026-53585 (MEDIUM), CVE-2026-53584 (MEDIUM), CVE-2026-53583 (MEDIUM).

Change Log

• CVE-2026-53587
• CVE-2026-53586
• CVE-2026-53585
• CVE-2026-53584
• CVE-2026-53583

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-53587
• https://nvd.nist.gov/vuln/detail/CVE-2026-53586
• https://nvd.nist.gov/vuln/detail/CVE-2026-53585
• https://nvd.nist.gov/vuln/detail/CVE-2026-53584
• https://nvd.nist.gov/vuln/detail/CVE-2026-53583

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.

[kgodara912]

Buddy build. The test failure was addressed in separate 3.0-dev branch PR and it was merged.

[kgodara912]

Buddy build with test PR as well as CVE patches on 3.0-dev branch.

[kgodara912]

All the patches match with respective upstream references except one which has one binary test file which is removed along with corresponding test case as rpm doesn't support binary file in patch. The security fix is taken as is. libgit2 test failure is already addressed in 3.0-dev branch but that is not yet propagated to fasttrack hence those test failures are seen in PR checks and buddy build. Once branches converse, those will go. The buddy build is already updated with the proper future conversion patches and it successful when this PR is run on top of 3.0-dev branch which has test fix. LGTM.