Skip to content

ci: pin tj-actions/changed-files to v46.0.1 SHA (GHSA-mrrh-fwg8-r2c3) - #342

Merged
chmaltsp merged 1 commit into
mainfrom
security-sweep/pin-tj-actions
Nov 10, 2026
Merged

chmaltsp merged 1 commit into
mainfrom
security-sweep/pin-tj-actions

Conversation

@chmaltsp

Copy link
Copy Markdown
Contributor

Summary

.github/workflows/automerge.yml referenced tj-actions/changed-files@v44, a mutable tag. This PR pins it to the commit for v46.0.1 (2f7c5bfce28377bc069a65ba478de0a74aa0ca32).

Why

GHSA-mrrh-fwg8-r2c3 / CVE-2025-30066: in March 2025 the tags of tj-actions/changed-files were re-pointed to a malicious commit (0e58ed8671d6b60d0890c21b07f8835ace038e67) that printed CI runner secrets into workflow logs. Because we followed a mutable tag, a tag move alone would have changed the code we run. Pinning to a full commit SHA prevents that. The same pin is already used in seamapi/docs.

Verification

  • gh api repos/tj-actions/changed-files/git/ref/tags/v46.0.1 resolves to 2f7c5bfce28377bc069a65ba478de0a74aa0ca32, which is the pinned SHA.
  • It is not the malicious commit 0e58ed86….
  • The commit is dated 2025-03-16T04:10:55Z, after the incident window (2025-03-14 to 2025-03-15) and after the upstream remediation. v46.0.1 is the version the advisory names as the patched release.

Compatibility (v44 to v46.0.1)

No change needed to automerge.yml. action.yml (inputs, outputs, runs.using: node20) is byte-for-byte identical between v44.5.7 and the pinned SHA, and this workflow only uses the files input and the any_changed output. The v45 and v46 release notes list dependency bumps and docs/security notices only. This job only runs for Dependabot (or seambot) PRs, so it will not run on this PR; the first such PR after merge is the real test.

Release

The commit type is ci:. .releaserc.json uses only @semantic-release/commit-analyzer with the default preset, under which ci: does not produce a release.

Other third-party actions still on mutable tags (not changed here)

  • DamianReeves/write-file-action@v1.3
  • NuGet/login@v1
  • balvajs/delete-stale-branches@v2
  • crazy-max/ghaction-import-gpg@v7
  • cycjimmy/semantic-release-action@v6
  • extractions/setup-just@v4
  • fountainhead/action-wait-for-check@v1.2.0
  • softprops/action-gh-release@v3
  • stefanzweifel/git-auto-commit-action@v7

Consider pinning these to SHAs as follow-up.

🤖 Generated with Claude Code

Pin tj-actions/changed-files to the v46.0.1 commit SHA instead of the
mutable v44 tag. The tag was re-pointed to a malicious commit in March
2025 (CVE-2025-30066). No input/output changes affect automerge.yml.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chmaltsp chmaltsp added the security-sweep Automated security sweep label Nov 10, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-10T19:35:54.232982Z 5e373a6 PR opened
🔒 Security Review ✅ Completed 2026-11-10T19:36:52.195481Z 5e373a6 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chmaltsp
chmaltsp merged commit 4dbe0fe into main Nov 10, 2026
14 checks passed
@chmaltsp
chmaltsp deleted the security-sweep/pin-tj-actions branch November 10, 2026 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

security-sweep Automated security sweep

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant