CVE-2025-30066: Embedded malicious code in tj-actions/changed-files
- Vendor
- tj-actions
CVE-2025-30066 is a supply-chain compromise of the tj-actions/changed-files GitHub Action affecting releases before version 46. On March 14–15, 2025, version tags v1 through v45.0.7 were redirected to a malicious commit containing modified updateFeatures code. The payload executed a Python script that extracted secrets from GitHub Actions runner process memory and wrote them into workflow logs using double Base64 encoding. Remote attackers could recover exposed credentials by reading those logs, with public repositories particularly exposed because their logs were publicly accessible. The action was referenced by more than 23,000 repositories, but this does not establish how many executed the malicious revision or leaked secrets.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Sensitive CI/CD credentials could be disclosed, including AWS access keys, GitHub personal access tokens, npm tokens, and private RSA keys. Public workflow logs could make those credentials available to unauthenticated readers; private workflow logs could expose them to users with log access. Depending on the stolen credentials' permissions and validity, subsequent abuse could enable repository takeover, malicious package publication, cloud resource access, or other downstream supply-chain compromise. CISA added the vulnerability to its Known Exploited Vulnerabilities catalog following evidence of active exploitation.
Mitigation
If you can’t patch tonight, do this now.
If a verified clean version cannot be deployed immediately, disable or remove the action across all branches, or block it using GitHub Actions allow-list settings. Preserve affected workflow logs securely for forensic analysis before deleting exposed logs to limit further disclosure. Pin actions to verified full-length commit SHAs rather than mutable tags or branches, and separately assess transitive dependencies. Minimize workflow token permissions and secret availability, prefer short-lived credentials, and monitor workflow and audit logs for suspicious activity. Outbound network restrictions alone do not prevent this attack because secrets can be disclosed through workflow logs.
Remediation
Patch, then assume compromise.
Update tj-actions/changed-files to version 46.0.1 or a later verified clean release, preferably referenced by its verified full-length immutable commit SHA. Replace any workflow references to the malicious revision, including references on non-default branches. Review historical workflow executions for compromised action use and secret disclosure. Revoke and rotate all credentials potentially exposed to affected executions, and investigate subsequent use of those credentials. Maintainers restored affected tags, but updating references alone does not invalidate previously leaked secrets.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-30066 exploited in the wild?
- Yes. As of Nov 12, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 18, 2025.
- Is there a public exploit for CVE-2025-30066?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-30066, the earliest disclosed May 14, 2026.
- Is there a patch for CVE-2025-30066?
- Update tj-actions/changed-files to version 46.0.1 or a later verified clean release, preferably referenced by its verified full-length immutable commit SHA. Replace any workflow references to the malicious revision, including references on non-default branches.
- What products are affected by CVE-2025-30066?
- tj-actions Changed-Files.
- How severe is CVE-2025-30066?
- CVE-2025-30066 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 72.1% (99th percentile) as of Nov 12, 2026.
Recent activity
31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.