[AutoPR- Security] Patch mysql for CVE-2026-63388, CVE-2026-63387, CVE-2026-63385, CVE-2026-63384, CVE-2026-63383, CVE-2026-63382, CVE-2026-63381, CVE-2026-63379 [HIGH]

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

Auto Patch mysql for CVE-2026-63388, CVE-2026-63387, CVE-2026-63385, CVE-2026-63384, CVE-2026-63383, CVE-2026-63382, CVE-2026-63381, CVE-2026-63379.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1190380&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 mysql for CVE-2026-63388 (HIGH), CVE-2026-63387 (MEDIUM), CVE-2026-63385 (HIGH), CVE-2026-63384 (MEDIUM), CVE-2026-63383 (HIGH), CVE-2026-63382 (HIGH), CVE-2026-63381 (MEDIUM), CVE-2026-63379 (MEDIUM).

Change Log

• CVE-2026-63388
• CVE-2026-63387
• CVE-2026-63385
• CVE-2026-63384
• CVE-2026-63383
• CVE-2026-63382
• CVE-2026-63381
• CVE-2026-63379

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-63388
• https://nvd.nist.gov/vuln/detail/CVE-2026-63387
• https://nvd.nist.gov/vuln/detail/CVE-2026-63385
• https://nvd.nist.gov/vuln/detail/CVE-2026-63384
• https://nvd.nist.gov/vuln/detail/CVE-2026-63383
• https://nvd.nist.gov/vuln/detail/CVE-2026-63382
• https://nvd.nist.gov/vuln/detail/CVE-2026-63381
• https://nvd.nist.gov/vuln/detail/CVE-2026-63379

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.

[Akhila Guruju (akhila-guruju)]

Patch Analysis:
CVE-2026-63379:
Backported: Yes. Hunk failed due to variation around patched lines.
Patch matches with upstream patch.

CVE-2026-63381:
Backported: No.
Upstream patch directly applies for buffer.c file.
The file test/regress_buffer.c is not present in azl source code.

CVE-2026-63382:
Backported: Yes. Hunk failed due to variation around patched lines.
Patch matches with upstream patch. 2 commits were included in a single patch.
The file test/regress_http.c is not present in azl source code.

CVE-2026-63383:
Backported: No.
Upstream patch applied cleanly.

CVE-2026-63384:
Backported: No.
Upstream patch applied cleanly.

CVE-2026-63385:
Backported: No.
Patch matches with upstream patch.
The file test/regress_http.c is not present in azl source code.

CVE-2026-63387:
Backported: No.
Upstream patch applied cleanly.

CVE-2026-63388:
Backported: No.
Patch matches with upstream patch.

Buddy Build has passed.
Patches apply cleanly.