CVE-2025-30066 · Severity: critical · CVSS 8.6 · Exploited in the wild · Published 2025-03-18
The tj-actions/changed-files GitHub Action was compromised by a threat actor who modified tags v1 through v45.0.7 to point to a malicious commit. The embedded malicious code (updateFeatures) allows remote attackers to exfiltrate secrets, such as AWS keys and GitHub PATs, by reading GitHub Actions workflow logs.
Quick answers
Is CVE-2025-30066 exploited in the wild?
Yes. CVE-2025-30066 is known to be exploited in the wild, first recorded on 18 March 2025. Treat it as urgent.
How severe is CVE-2025-30066?
Critical severity, with a CVSS score of 8.6, published 18 March 2025.
Which products and versions are affected?
tj-actions changed-files v1 through v45.0.7.
Is there a fix for CVE-2025-30066?
A patch was published on 2025-03-19: Version 46 and later are considered safe. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-30066 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2025-30066?
Check whether you run Tj-Actions changed-files GitHub Action. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Affected products
tj-actions changed-files v1 through v45.0.7
Timeline
2025-03-14: exploited: Malicious code injected into tags v1 through v45.0.7 by a threat actor.
2025-03-18: disclosed: CVE-2025-30066 published.
2025-03-18: kev added: Added to CISA Known Exploited Vulnerabilities (KEV) catalog.
2025-03-19: patched: Version 46 and later are considered safe.