Supply Chain Security Risk: GitHub Action tj-actions/changed-files Compromised
CVE-2025-30066 in the popular tj-actions/changed-files GitHub Action leaked CI/CD secrets through build logs, echoing earlier supply-chain compromises and reinforcing the need for pinned action references.
Summary written by editorial AI · Source link below
On March 14th, 2025, security researchers discovered a critical software supply chain vulnerability in the widely-used GitHub Action tj-actions/changed-files ( CVE-2025-30066 ). This vulnerability allows remote attackers to expose CI/CD secrets via the action's build logs. The issue affects users who rely on the tj-actions/changed-files action in GitHub workflows to track changed files within a pull request. Due to the compromised action, sensitive CI/CD secrets are being inadvertently logged in
Editorial Analysis
Third-party GitHub Actions are embedded across thousands of enterprise pipelines; a single compromised action can expose credentials at scale, making this a systemic supply-chain risk.
Pin all GitHub Actions to immutable commit SHAs, rotate any secrets potentially exposed through tj-actions/changed-files, and audit build logs for credential leakage.
A widely-used CI/CD component was compromised, potentially exposing pipeline credentials—review your software supply-chain controls.
Forward-looking interpretation drafted by editorial AI under human review — not a reproduction of the source. See methodology.
External link — opens at Aqua Security in a new tab.
More from the DevSecOps Desk
- Nearly 1.5 million exposed secrets targeted in new revocation program4d
- From Lab to Reality: A Practical Evaluation of Deep Learning Models and LLMs for Vulnerability Detection4d
- A.S.E 2.0: Understanding How Repository Context Impacts the Security of LLM-Generated Code4d
- A Hybrid Approach for Automated Security Pattern Recovery4d
- Chainguard endpoints now handle breaking changes5d