How severe is CVE-2025-30066?

CVE-2025-30066 has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-30066?

CVE-2025-30066 affects the following packages: tj-actions/changed-files (GitHub Actions). Ecosystems affected: GitHub Actions.

How do I fix CVE-2025-30066?

Update tj-actions/changed-files to version 46.0.1 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2025-30066 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-30066 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-30066?

CVE-2025-30066 has an EPSS (Exploit Prediction Scoring System) score of 91.5%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2025-30066 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-30066 (tj-actions/changed-files GitHub Action Embedded Malicious Code Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-03-18. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-04-08. The required action was: 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. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-30066?

CVE-2025-30066 is classified as CWE-506 (CWE-506). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-30066 published, and has it been updated?

CVE-2025-30066 was published on March 15, 2025 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2025-03-18 — agencies required to remediate by 2025-04-08

📦 GitHub Actions

CVE-2025-30066

HIGH

tj-actions changed-files through 45.0.7 allows remote attackers to discover secrets by reading actions logs.

Also known asGHSA-mrrh-fwg8-r2c3

Published

Mar 15, 2025

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

91.5%probability of exploitation in next 30 days

Very High Risk100th percentile-0.29%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦tj-actions/changed-files

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects GitHub Actions packages — download data is not available via public APIs for these ecosystems.

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦GitHub Actions	`tj-actions/changed-files`	all versions	46.0.1

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-30066 in your stack?

O3 detects CVE-2025-30066 across GitHub Actions dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works

CVSS Score

8.6/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction

None

S:Scope

Changed

C:Confidentiality

High

I:Integrity

None

A:Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

CWE Classification

CWE-506CWE-506

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

changed-files

6.1/10

Code-Review0/10

Maintained10/10

Branch-Protection3/10

Assessed Jun 1, 2026

Timeline

Disclosed

Mar 15, 2025

KEV added

Mar 18, 2025

Last updated

Apr 10, 2026

Identifiers

CVE-2025-30066

GHSA-mrrh-fwg8-r2c3

Data from OSV.dev, enriched by O3 Security. Refreshed hourly.