Summary
tj-actions changed-files through 45.0.7 allows remote attackers to discover secrets by reading actions logs.
Impact
- Type of vulnerability: Supply chain attack, Secrets exposure, Information leakage
- Who is impacted:
- Over 23,000 repositories using tj-actions/changed-files.
- Organizations with public repositories are at the highest risk, as their logs may already be compromised.
- Potential consequences:
- Theft of CI/CD secrets (API keys, cloud credentials, SSH keys).
- Unauthorized access to source code, infrastructure, and production environments.
- Credential leaks in public repositories, enabling further supply chain attacks.
CVE-2025-30066 has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (46.0.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-30066? CVE-2025-30066 is a high-severity security vulnerability in tj-actions/changed-files (actions), affecting versions <= 45.0.7. It is fixed in 46.0.1.
- How severe is CVE-2025-30066? CVE-2025-30066 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of tj-actions/changed-files are affected by CVE-2025-30066? tj-actions/changed-files (actions) versions <= 45.0.7 is affected.
- Is there a fix for CVE-2025-30066? Yes. CVE-2025-30066 is fixed in 46.0.1. Upgrade to this version or later.
- Is CVE-2025-30066 exploitable, and should I be worried? Whether CVE-2025-30066 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-30066 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-30066? Upgrade
tj-actions/changed-filesto 46.0.1 or later.