Patch python3 for CVE-2025-8194 [High]

[Kanishk-Bansal]

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?

• Address CVE-2025-8194 using Upstream Patch Reference: [3.9] gh-130577: tarfile now validates archives to ensure member offsets are non-negative (GH-137027) python/cpython#137645
• Change in the expression: %{with_check}

Change Log

• CVE-2025-8194

Does this affect the toolchain?

YES

Associated issues

• #xxxx

Links to CVEs

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

Test Methodology

• Pipeline build id: Buddy Build

[Kanishk-Bansal]

rpmspec was not able to parse the spec

• Original: %if %{with_check}

  • This condition is true if the macro with_check is defined and non-zero. If with_check is not defined, this can produce an error like it is creating right now when we are doing rpmspec parse.

• Changed to: %if 0%{?with_check}

  • 0%{?with_check} safely expands to 0 if with_check is not defined (so, false), or to the value of with_check if it is defined (still works as before if set).
  • The ? in %{?with_check} means "use the value if defined, otherwise nothing."
  • Prefixing with 0 ensures the macro always expands to a valid number (0/1), avoiding errors if undefined.

[Kanishk-Bansal]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Kanishk-Bansal]

the patch applies cleanly w.r.t upstream patch python/cpython#137645
No modification was needed.

[Kanishk-Bansal]

vitess, rpm-ostree, prometheus-process-exporter, moby-runc, libguestfs, pygobject3 are known failures.
This is not due to regression by this patch

[realsdx]

• Patch applies cleanly

• Security tag exists
• Release bump & Changelog
• Buddy Build
• No new ptest regression
  Signed-off-by: @realsdx

[CBL-Mariner-Bot]

Auto cherry-pick results:

• main ✅ -> [AUTO-CHERRYPICK] Patch python3 for CVE-2025-8194 [High] - branch main #14789

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=944855&view=results