[Medium] Patch python-virtualenv for CVE-2026-1703 & CVE-2026-24049

[BinduSri-6522866]

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?
Patch python-virtualenv for CVE-2026-1703 [Low]:

• Patch modified: Yes
• In pip-24.2-py3-none-any.whl [CVE-2026-1703v1.patch] the news/+1ee322a1.bugfix.rst new path is not added in patch from upstream patch to maintain compatibility with existing virtualenv cleanup behavior after tightening path validation logic (commonpath). This avoids leaving non-runtime artifacts in site-packages during pip uninstall and allows existing tests to pass without modifying test code.
• Astrolabe patch reference: https://github.com/pypa/pip/commit/8e227a9be4faa9594e05d02ca05a413a2a4e7735.patch

Patch python-virtualenv for CVE-2026-24049 [Medium]:

• Patch modified: Yes
• docs/news.rst and tests/commands/test_unpack.py files are not present in python-virtualenv source tarball, so patch didn't apply for these two files.
• Astrolabe patch reference: https://github.com/pypa/wheel/commit/7a7d2de96b22a9adf9208afcc9547e1001569fef.patch

Change Log

• new file: ../SPECS/python-virtualenv/CVE-2026-1703v0.patch
• new file: ../SPECS/python-virtualenv/CVE-2026-1703v1.patch
• new file: ../SPECS/python-virtualenv/CVE-2026-1703v2.patch
• new file: ../SPECS/python-virtualenv/CVE-2026-24049v0.patch
• new file: ../SPECS/python-virtualenv/CVE-2026-24049v1.patch
• new file: ../SPECS/python-virtualenv/CVE-2026-24049v2.patch
• modified: ../SPECS/python-virtualenv/python-virtualenv.spec

Does this affect the toolchain?

NO

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-1703
• https://nvd.nist.gov/vuln/detail/CVE-2026-24049

Test Methodology

• Local Build:
  python-virtualenv-20.26.6-3.cm2.src.rpm.log
  python-virtualenv-20.26.6-3.cm2.src.rpm.test.log
• Patch applies cleanly:

• Installation & Uninstallation check:

[mfrw]

• Patches look good w.r.t upstream
• Patches apply cleanly
• Test build passes link
  Signed-Off By: @mfrw

[kgodara912]

Patches are simple modifications. Currently this is the way the embedded packages are patched though we want to improve the method. Buddy build is successful. LGTM.