CVE-2025-30066 tj-actions/changed-files GitHub Action Embedded Malicious Code Vulnerability
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.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 18 Mar 2025.
- Rated High severity (CVSS 8.6, scored by Vendor).
- It has been in the catalogue for 598 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
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.)
Affected Versions
| Product | Versions |
|---|---|
| tj-actions changed-files | 1 to before 46 |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for tj-actions changed-files GitHub Action. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
Fix it
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.
Vulnerability Management - 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
Vendor Advisories
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
More Exploited tj-actions Flaws
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2025-30066 and every other exploited flaw on the list.
Sources
- CISA Known Exploited Vulnerabilities catalogue
- NVD: CVE-2025-30066
- CVE record: CVE-2025-30066
- FIRST EPSS
- github.com/github/docs/blob/962a1c8dccb8c0f66548b324e5b921b5e4fbc3d6/content/actions/security-for-gi
- github.com/tj-actions/changed-files/issues/2463
- stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised
- semgrep.dev/blog/2025/popular-github-action-tj-actionschanged-files-is-compromised/
- news.ycombinator.com/item?id=43368870
- web.archive.org/web/20250315060250/https://github.com/tj-actions/changed-files/issues/2463
- news.ycombinator.com/item?id=43367987
- github.com/rackerlabs/genestack/pull/903
