Repository navigation
Conversation
Print sys.version in the harden-pip action and fail when the interpreter is older than the first release of its minor series that rejects the compromised eMudhra/emSign intermediate CA keys.
Contributor
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Refs #3195
The Python releases 3.15.2, 3.14.10, 3.13.18, 3.12.16 and 3.11.18 (announcement, CVE-2026-115557) make the
sslmodule reject the compromised eMudhra intermediate keys. An older interpreter on a runner (for example a stale tool cache) silently keeps trusting them, and nothing in CI notices.This PR makes
harden-pipcheck the interpreter first. The newcheck_python_patched.pyprintssys.versionand fails when the interpreter is older than the first fixed release of its minor series:3.14t,3.15t) report the same version tuple.::warning::, because no fixed release is known there yet. ExtendFIXED_MICROonce one exists.The check lives in
harden-pipbecause nearly every job that sets up Python calls it right aftersetup-python(wheel builds and tests, coverage, sdist tests, release, pre-commit, lychee, nightly). The script sits next to the action and runs throughGITHUB_ACTION_PATH, so it matches the action's commit at the call sites that use$/.github/actions/harden-pip.Not covered: the
uv-based jobs (bandit,griffe-api-check), the Miniforge docs build, and the Python inside the cibuildwheel containers.The
actions/python-versionsmanifest used bysetup-pythonalready lists all five fixed releases as stable. Self-hosted runners that servesetup-pythonfrom/opt/hostedtoolcachewill fail the check if they still carry an older patch release, which is the intended outcome.Also adds
.github/actions/**to theT201(print) per-file ignores inruff.toml, matchingci/**.Checklist
ci/tools/tests/test_check_python_patched.py; the action step is exercised by every job that callsharden-pip.)