[AutoPR- Security] Patch openssl for CVE-2026-75803, CVE-2026-63076, CVE-2026-63075, CVE-2026-63074, CVE-2026-63073, CVE-2026-63072, CVE-2026-54874 [HIGH]

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

Auto Patch openssl for CVE-2026-75803, CVE-2026-63076, CVE-2026-63075, CVE-2026-63074, CVE-2026-63073, CVE-2026-63072, CVE-2026-54874.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1191350&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 openssl for CVE-2026-75803 (MEDIUM), CVE-2026-63076 (HIGH), CVE-2026-63075 (MEDIUM), CVE-2026-63074 (MEDIUM), CVE-2026-63073 (MEDIUM), CVE-2026-63072 (MEDIUM), CVE-2026-54874 (MEDIUM).

Change Log

• CVE-2026-75803
• CVE-2026-63076
• CVE-2026-63075
• CVE-2026-63074
• CVE-2026-63073
• CVE-2026-63072
• CVE-2026-54874

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-75803
• https://nvd.nist.gov/vuln/detail/CVE-2026-63076
• https://nvd.nist.gov/vuln/detail/CVE-2026-63075
• https://nvd.nist.gov/vuln/detail/CVE-2026-63074
• https://nvd.nist.gov/vuln/detail/CVE-2026-63073
• https://nvd.nist.gov/vuln/detail/CVE-2026-63072
• https://nvd.nist.gov/vuln/detail/CVE-2026-54874

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.

[Kanishk Bansal (Kanishk-Bansal)]

Full Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1191517&view=results

[jykanase]

• All patches applied cleanly.
• patch applied during the build (check rpm.log)
• patch include an upstream reference.

Buddy Build passed.

[Kanishk Bansal (Kanishk-Bansal)]

Arch	Test	Run	Test_Mariner	Test results
amd64	verify_openssl_basic	1192108	✅ succeeded	1/1 passed
amd64	verify_openssl_speed_test	1192109	✅ succeeded	1/1 passed
amd64	verify_golang_sys_crypto	1192110	✅ succeeded	1/1 passed
arm64	verify_openssl_basic	1192111	✅ succeeded	1/1 passed
arm64	verify_openssl_speed_test	1192112	✅ succeeded	1/1 passed
arm64	verify_golang_sys_crypto	1192113	✅ succeeded	1/1 passed

The base branch was changed.

[Kanishk Bansal (Kanishk-Bansal)]

Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1195089&view=results