# CVE-2025-30066: tj-actions/changed-files GitHub Action Embedded Malicious Code

> Attackers can steal secrets and execute code via maliciously modified GitHub Actions tags in tj-actions changed-files.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 18 Mar 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Mar 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-mrrh-fwg8-r2c3

## What is CVE-2025-30066?

CVE-2025-30066 is a high-severity vulnerability in tj-actions changed-files, published on 15 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.)

Weakness: CWE-506 (Embedded Malicious Code)

## Which versions are affected by CVE-2025-30066?

1 open source package ship an affected version, including tj-actions/changed-files. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tj-actions/changed-files` | GitHub Actions | All versions | 46.0.1 |

Products: Tj-Actions Changed-Files.

## How do I fix CVE-2025-30066?

Upgrade tj-actions/changed-files to 46.0.1 or later. US federal agencies must fix it by 8 Apr 2025.

## Is CVE-2025-30066 being exploited?

Yes. Attackers have exploited CVE-2025-30066 in the wild since at least 18 Mar 2025.

Public exploit code:

- https://github.com/Checkmarx/Checkmarx-CVE-2025-30066-Detection-Tool (github_poc): https://github.com/Checkmarx/Checkmarx-CVE-2025-30066-Detection-Tool
- Test repo: simulates CVE-2025-30066 style compromised GitHub Action (for security research/testing chainradar) (github_poc): https://github.com/Super-Vulnerable-Org/compromised-action

## Other vulnerabilities in tj-actions changed-files

- [CVE-2023-51664](https://insights.sbomify.com/CVE-2023-51664/): tj-actions/changed-files command injection in output filenames (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30066 and fix it if it is affected.

What it is: CVE-2025-30066 is a high-severity vulnerability in tj-actions changed-files, published on 15 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-30066 in the wild since at least 18 Mar 2025.

Affected packages and fixed versions:
- tj-actions/changed-files (GitHub Actions): affected all versions; fixed in 46.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-30066/ (Markdown: https://insights.sbomify.com/CVE-2025-30066/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-30066
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-30066
- OSV: https://osv.dev/vulnerability/CVE-2025-30066

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-30066/
Summaries are generated and may contain mistakes; the official description above is the record.