CVE-2025-30066
tj-actions/changed-files GitHub Action Embedded Malicious Code Vulnerability
tj-actions changed-files GitHub Action
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.)
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 18 March 2025. US federal agencies were required to remediate it by 8 April 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 72.1%, which is higher than 99.4% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Frequently asked questions
Is CVE-2025-30066 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-30066.
What does CVE-2025-30066 affect?
CVE-2025-30066 affects tj-actions changed-files GitHub Action. 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.)
How severe is CVE-2025-30066?
CVE-2025-30066 is rated HIGH with a CVSS base score of 8.6. EPSS puts the probability of exploitation in the next 30 days at 72.1%, higher than 99.4% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 8 April 2025.
How should organisations respond to CVE-2025-30066?
Apply the vendor patch for tj-actions changed-files GitHub Action as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.