Skip to content

fix(security): pin GitHub Actions to commit SHAs in CI/publish workflow#198

Open
XananasX7 wants to merge 1 commit into
google:mainfrom
XananasX7:fix/security-pin-actions
Open

fix(security): pin GitHub Actions to commit SHAs in CI/publish workflow#198
XananasX7 wants to merge 1 commit into
google:mainfrom
XananasX7:fix/security-pin-actions

Conversation

@XananasX7

Copy link
Copy Markdown

Summary

This workflow uses mutable tag references for GitHub Actions, including etils-actions/pypi-auto-publish@v1 — a third-party action. If the tag is silently redirected (compromised maintainer, repo takeover, tag deletion/recreation), malicious code runs in the job that holds PYPI_API_TOKEN, enabling a backdoored PyPI release and a supply-chain attack on downstream users.

Changes

All action references pinned to immutable commit SHAs (with tag preserved as comment for readability):

  • actions/checkout@v4 → SHA-pinned
  • actions/setup-python@v5 → SHA-pinned
  • etils-actions/pypi-auto-publish@v1@e3c4b4afc3a5b12a44734da938741995538e8223
  • styfle/cancel-workflow-action@0.7.0 → SHA-pinned (where applicable)

This follows the GitHub security hardening guide.

Tag-pinned actions (including etils-actions/pypi-auto-publish@v1) can
be silently redirected to malicious code. Pinning to SHA hashes ensures
the action code is immutable and tamper-proof, preventing supply-chain
attacks via `PYPI_API_TOKEN`.
@google-cla

google-cla Bot commented Jun 28, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant