Known exploited · tj-actions
CVE-2025-30066: tj-actions/changed-files GitHub Action Embedded Malicious Code Vulnerability
What it is
tj-actions/changed-files GitHub Action contains an embedded malicious code vulnerability that allows a remote attacker to discover secrets by reading Github Actions Workflow Logs. These secrets may include, but are not limited to, valid AWS access keys, GitHub personal access tokens (PATs), npm tokens, and private RSA keys.
- Vendor
- tj-actions
- Product
- changed-files GitHub Action
- Added to KEV
- March 18, 2025
- CISA due date
- April 8, 2025
- Ransomware use
- Unknown
- Weakness
- CWE-506: Embedded Malicious Code
What CISA requires
Apply mitigations as set forth in the CISA instructions linked below. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Forensic triage
No
What to do now
- Find every instance of changed-files GitHub Action you run, including the forgotten ones, and check its version against the vendor advisory.
- Apply the vendor's fix or mitigation, before April 8, 2025 if you are bound by CISA's deadline, sooner if it faces the internet.
- Assume it was tried against you already: look for signs of exploitation from the date it was added, not from the day you patched.
References
H2 Security
Not sure you are clear?
We check where you run it, patch or mitigate with your team, and look for signs it was already used against you.
Talk to our teamT Academy
Train the engineers who fix it
Security engineering on real hosts in the browser, every objective checked on the machine. The first two lessons of Linux 1 are free.
Start freeSource: CISA Known Exploited Vulnerabilities Catalog (public domain), catalog version 2026.10.01.