CVE-2025-30066

tj-actions changed-files GitHub Action: tj-actions/changed-files GitHub Action Embedded Malicious Code

As of , CVE-2025-30066 in tj-actions changed-files GitHub Action is on CISA's list of exploited vulnerabilities: CISA listed it on . Our patch-first group: Patch this week.

Exploited
Yes: CISA listed it on 18 March 2025
US federal deadline
8 April 202521 days after CISA listed it. US federal civilian agencies must fix it by then.
Used in ransomware campaigns
Not known to CISA
EPSS score
0.72Higher than 99% of the CVEs EPSS scores. EPSS estimates the chance of exploitation activity in the next 30 days.
Public exploit
None foundNeither Metasploit nor Exploit-DB lists one.
Fix
Vendor advice: github.comLinks below, from CISA's entry.

What CISA says to do

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's required action

What the flaw 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.

CISA's 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.)

The CVE record's description, from mitre

CVE published
15 March 2025
Assigned by
mitre
CVSS
8.6 High (CVSS 3.1, from the CNA)
CWE-506
Embedded Malicious Code
CISA SSVC, exploitation
active
CISA SSVC, automatable
yes
CISA SSVC, technical impact
partial

Timeline

  1. The CVE record was published.
  2. CISA added it to its list of exploited vulnerabilities.
  3. CISA changed its entry. Edited: notes and description.
  4. CISA changed its entry. Edited: notes.
  5. CISA changed its entry. Edited: required action.
  6. The US federal deadline to fix it.

Read further