[AutoPR- Security] Patch python3 for CVE-2026-9669, CVE-2026-6879, CVE-2026-6100, CVE-2026-4786, CVE-2026-4360, CVE-2026-3644, CVE-2026-3276, CVE-2026-3087, CVE-2026-2297, CVE-2026-12003, CVE-2026-11972, CVE-2026-0864 [HIGH]

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

Auto Patch python3 for CVE-2026-9669, CVE-2026-6879, CVE-2026-6100, CVE-2026-4786, CVE-2026-4360, CVE-2026-3644, CVE-2026-3276, CVE-2026-3087, CVE-2026-2297, CVE-2026-12003, CVE-2026-11972, CVE-2026-0864.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1175556&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 python3 for CVE-2026-9669 (MEDIUM), CVE-2026-6879 (LOW), CVE-2026-6100 (HIGH), CVE-2026-4786 (HIGH), CVE-2026-4360 (LOW), CVE-2026-3644 (MEDIUM), CVE-2026-3276 (MEDIUM), CVE-2026-3087 (MEDIUM), CVE-2026-2297 (MEDIUM), CVE-2026-12003 (MEDIUM), CVE-2026-11972 (HIGH), CVE-2026-0864 (MEDIUM).

Change Log

• CVE-2026-9669
• CVE-2026-6879
• CVE-2026-6100
• CVE-2026-4786
• CVE-2026-4360
• CVE-2026-3644
• CVE-2026-3276
• CVE-2026-3087
• CVE-2026-2297
• CVE-2026-12003
• CVE-2026-11972
• CVE-2026-0864

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-9669
• https://nvd.nist.gov/vuln/detail/CVE-2026-6879
• https://nvd.nist.gov/vuln/detail/CVE-2026-6100
• https://nvd.nist.gov/vuln/detail/CVE-2026-4786
• https://nvd.nist.gov/vuln/detail/CVE-2026-4360
• https://nvd.nist.gov/vuln/detail/CVE-2026-3644
• https://nvd.nist.gov/vuln/detail/CVE-2026-3276
• https://nvd.nist.gov/vuln/detail/CVE-2026-3087
• https://nvd.nist.gov/vuln/detail/CVE-2026-2297
• https://nvd.nist.gov/vuln/detail/CVE-2026-12003
• https://nvd.nist.gov/vuln/detail/CVE-2026-11972
• https://nvd.nist.gov/vuln/detail/CVE-2026-0864

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.

[Aditya Singh (v-aaditya)]

Re-triggered Buddy Build after updating patch for CVE-2026-11972 and it has passed.

Modification details -
In SPECS/python3/CVE-2026-11972.patch the test file Lib/test/test_tarfile.py has a function which is using a utility function from Lib/test/support/__init__.py in upstream source code but in our source code it is not yet defined -

@support.subTests('format', [tarfile.GNU_FORMAT, tarfile.PAX_FORMAT])

This utility function's definition has been included in Lib/test/support/__init__.py file similar to upstream.
The same function is also being used in SPECS/python3/CVE-2026-4360.patch which was also added in this PR, so this fix will also work for this patch.

[Aditya Singh (v-aaditya)]

Updated patch for CVE-2026-0864. The AI patch was completely incorrect and was carrying fix for a different CVE-2026-11940 altogether.

Modification details -

1. Now the patch completely matches with respective upstream patch.
2. The upstream patch applies cleanly without any changes
3. The patch has upstream patch reference.
4. Offset changed for CVE-2026-11972 and CVE-2025-4360 patch because of above modification, so updated them as well.

Upstream Patch reference - https://github.com/python/cpython/commit/db4a157c790479710a1a840d7937c5c815a6f8b6.patch

Buddy Build has been re-triggered and it has passed.
The patches apply cleanly. (Checked .rpm.log)
The ptest has also passed. (Checked .test.log)

[Aditya Singh (v-aaditya)]

I have not triggered a Buddy Build as only upstream patch reference has been updated in the patch header of CVE-2026-0864.

[Kanishk Bansal (Kanishk-Bansal)]

/azurepipelines run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.