[Medium] patch python3 for CVE-2025-4516

[jykanase]

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

patch python for CVE-2025-4516

Change Log

• python3.spec

Does this affect the toolchain?

YES/NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2025-4516

Test Methodology

• Pipeline build id: xxxx

[kgodara912]

Patch matches with upstream reference. Buddy build

[kgodara912]

This upstream reference is still in open state. Please wait till the upstream reference is merged as upstream reviewers may request changes for any potential issues in the above patch. Also, as Python3.9 is still in maintenance, if new python3.9 release is done after the upstream reference is merged, we should switch to upstream release instead of taking patches. As per Debian, python3.9 (Minor issue, likely DoS-only, fix along with next update)