CVE-2025-30066: tj-actions/changed-files GitHub Action Embedded Malicious Code
tj-actions changed-files GitHub Action · listed in the CISA catalog of actively exploited vulnerabilities since 2025-03-18.
- CVSS v3.1 (CVE record)
- 8.6
- high
- EPSS (exploit probability, 30 days)
- 72%
- higher than 99.4% of all CVEs
- Added to CISA KEV
- 2025-03-18
- US federal due date 2025-04-08
- Automatable (CISA SSVC)
- yes
- technical impact: partial
CVE-2025-30066 explained
CVE-2025-30066 affects the tj-actions changed-files GitHub Action before version 46. A threat actor modified existing release tags to point at a commit with malicious code, which let remote attackers obtain secrets by reading GitHub Actions logs. CISA lists it as known exploited, and any workflow that ran an affected tag may have exposed its CI/CD secrets.
Impact
Attackers can obtain secrets from workflows that ran the compromised action, because the malicious code made them readable in Actions logs. Exploitation needs no privileges or user interaction and works over the network. The scope is changed and confidentiality impact is high. CISA rates it as automatable, so attackers can exploit it at scale, with partial technical impact. CISA confirms active exploitation.
Who is affected
The CVE record lists tj-actions changed-files versions ≥ 1, < 46 as affected, meaning from 1 up to but not including 46. The description states the tags were modified on 2025-03-14 and 2025-03-15 to point at malicious commit 0e58ed8. The record names 46 as the fixed version.
Written with AI from the data on this page and checked against it automatically.
Official description
tj-actions changed-files before 46 allows remote attackers to discover secrets by reading actions logs. (The tags v1 through v45.0.7 were affected on 2025-03-14 and 2025-03-15 because they were modified by a threat actor to point at commit 0e58ed8, which contained malicious updateFeatures code.)
CISA required action: 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.
CISA notes
- This vulnerability affects a common open-source project, third-party library, or a protocol used by different products. For more information, please see: CISA Mitigation Instructions: cisa.gov/news-events/alerts/2025/03/18/supply-chain-compr…
- Additional References: github.com/tj-actions/changed-files/blob/45fb12d…/README.md
- nvd.nist.gov/vuln/detail/CVE-2025-30066
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- tj-actions changed-filesAffectedFixed in
- ≥ 1, < 46
- 46
| Product | Affected | Fixed in |
|---|---|---|
| tj-actions changed-files |
|
|
How to fix it
- Update to a fixed version: 46.
- CISA's deadline for US federal agencies: 2025-04-08 (passed) – a useful benchmark for everyone else, too.
What to do
- Update all workflows that use tj-actions changed-files to version
46or later. - Review GitHub Actions logs from runs on 2025-03-14 and 2025-03-15 for exposed secrets.
- Rotate any secrets, tokens and credentials available to workflows that ran an affected version.
- Apply CISA's mitigations and the vendor's instructions, following BOD 22-01 guidance where it applies.
- Remove or restrict access to workflow logs that may contain leaked secrets.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Partial – limited control or information
Weakness: CWE-506 Embedded Malicious Code
Questions about CVE-2025-30066
- Which version fixes CVE-2025-30066?
- The CVE record names version
46as the fixed version. All versions from1up to but not including46are listed as affected. - Is this vulnerability exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-03-18, with a US federal due date of 2025-04-08. Ransomware use is listed as unknown.
- Is updating enough?
- No. Updating stops further exposure, but secrets already written to logs may have been read. Rotate credentials used by affected workflow runs and review their logs.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.