← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2025-30066 exploited? Yes: in CISA KEV since 18 Mar 2025

Gociux · tj-actions changed-files GitHub Action · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2025-30066, tj-actions/changed-files GitHub Action Embedded Malicious Code Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 18 Mar 2025, 3 days after it was published. It affects tj-actions changed-files GitHub Action. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 18 Mar 2025
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity8.6CVSS 3.1 · high
US federal due8 Apr 2025BOD 22-01 deadline

What it 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.

Vendortj-actions (1 exploited CVE in KEV)
Productchanged-files GitHub Action
Vulnerabilitytj-actions/changed-files GitHub Action Embedded Malicious Code Vulnerability
WeaknessCWE-506
Published15 Mar 2025
Added to KEV18 Mar 2025
Reported by (CNA)mitre

What to do

  1. Check whether you run it. Look for changed-files GitHub Action in your asset inventory, including appliances and cloud images. Stack check lists every exploited tj-actions CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 15 Mar 2025.
  4. Get told next time. Email alerts when CISA adds a CVE for tj-actions.

References

Questions

Is CVE-2025-30066 being exploited?

Yes. CISA added CVE-2025-30066 to the Known Exploited Vulnerabilities catalog on 18 Mar 2025, which means there is reliable evidence of exploitation in the wild.

Is CVE-2025-30066 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2025-30066?

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. Check tj-actions's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected changed-files GitHub Action and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in March 2025 · act-now radar.

Running tj-actions in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →