CVE-2025-30066
CVE-2025-30066 is a security flaw in tj-actions changed-files GitHub Action. A tampered release of tj-actions changed-files GitHub Action was published with malicious code built in. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 18 Mar 2025.[1]
tj-actions changed-files GitHub Action is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Fixed in version 46 of changed-files.
Description
CISA calls it a tj-actions/changed-files gitHub action embedded malicious code in tj-actions changed-files GitHub Action. In its words: “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.”[1]
The underlying weakness is CWE-506, in MITRE’s list of common software weaknesses.[2]
It scores 8.6 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by NVD using CVSS 3.1.[2]
Affected versions
NVD’s record lists one fixed version: everything before it is affected.[2]
| Product | Fixed in |
|---|---|
| changed-files | 46 |
Most families won’t have tj-actions changed-files GitHub Action; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 18 Mar 2025, 3 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 8 Apr 2025 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 72%. That’s in the top 1% of the flaws it scores.[4]
CISA assesses it as automatable: attackers can run it against many targets at once.
CISA doesn’t say who was attacked, or how.
Fix
tj-actions has published a fix or advice.[3] CISA’s required action: “Apply mitigations as set forth in the CISA instructions linked below.”[1]
- Check whether you use it.tj-actions changed-files GitHub Action is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed (fixed in version 46 of changed-files), or not in use. CISA gave US government agencies until 8 Apr 2025 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 8.6.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at 72%.[4] |
See also
Similar flaws
- CVE-2026-8398, Daemon Tools Lite: tools lite embedded malicious code ·
- CVE-2026-48027, Nx Console: console embedded malicious code ·
- CVE-2026-45321, TanStack: unspecified ·
- CVE-2026-33634, Aquasecurity Trivy: embedded malicious code ·
- CVE-2025-54313, Prettier eslint-config-prettier: embedded malicious code ·
Added the same day
- CVE-2025-24472, Fortinet FortiOS and FortiProxy: authentication bypass ·
References
- ^ Cybersecurity and Infrastructure Security Agency. “tj-actions/changed-files GitHub Action Embedded Malicious Code Vulnerability”. Known Exploited Vulnerabilities Catalog, added 18 Mar 2025.
- ^ National Institute of Standards and Technology. “CVE-2025-30066 Detail”. National Vulnerability Database, published 15 Mar 2025.
- ^ tj-actions. Advisories and fixes: sysdig.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.721, percentile 99.4, 31 Oct 2026.
- CVE Program. “CVE-2025-30066”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.