CVE-2025-30066
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.)
do firstApply 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.
Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.
Cloudflare · 1 rule (Disabled) · since 27 May 2025
- GitHub Action - Remote Code Execution - CVE:CVE-2025-30066 · Cloudflare Managed Ruleset
Also consider: patch · enable the vendor rule in block mode · SBOM · artifact signing
Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-30066 being exploited?
Yes. CVE-2025-30066 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-30066?
CVE-2025-30066 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-30066?
Yes. A fix has been recorded for CVE-2025-30066. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-30066 affect?
CVE-2025-30066 affects tj-actions:changed-files. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 1 and < 46
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- partial
Assessed by CISA 22 Mar 2025 (SSVC 2.0.3).
timeline
- 15 Mar 2025Published
- 18 Mar 2025Added to CISA KEV (exploited in the wild) · 3 days later
- 18 Mar 2025First proof-of-concept repository on GitHub (unvetted) · same day later
- 22 Mar 2025CISA SSVC assessment: exploitation active · 4 days later
- 8 Apr 2025CISA remediation due date (US federal agencies) · 17 days later
- 26 Feb 2026CVE record last updated · 325 days (about 11 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
also known as
- Linkgithub.com /github/docs/blob/962a1c8dccb8c0f66548b324e5b921b5e4fbc3d6/content/actions/secur
- Linkgithub.com /tj-actions/changed-files/issues/2463
- Linkstepsecurity.io /blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised
- Linksemgrep.dev /blog/2025/popular-github-action-tj-actionschanged-files-is-compromised/
- Linknews.ycombinator.com /item?id=43368870
- Linkweb.archive.org /web/20250315060250/https://github.com/tj-actions/changed-files/issues/2463
- Linknews.ycombinator.com /item?id=43367987
- Linkgithub.com /rackerlabs/genestack/pull/903
Show 13 more
- Linkgithub.com /chains-project/maven-lockfile/pull/1111
- Linksysdig.com /blog/detecting-and-mitigating-the-tj-actions-changed-files-supply-chain-attack-
- Linkgithub.com /espressif/arduino-esp32/issues/11127
- Linkgithub.com /modal-labs/modal-examples/issues/1100
- Linkgithub.com /tj-actions/changed-files/issues/2464
- Linkgithub.com /tj-actions/changed-files/blob/45fb12d7a8bedb4da42342e52fe054c6c2c3fd73/README.m
- Linkwiz.io /blog/github-action-tj-actions-changed-files-supply-chain-attack-cve-2025-30066
- Linkstream.security /post/github-action-supply-chain-attack-exposes-secrets-what-you-need-to-know-an
- Linksweet.security /blog/cve-2025-30066-tj-actions-supply-chain-attack
- Linkgithub.com /tj-actions/changed-files/issues/2477
- Linkblog.gitguardian.com /compromised-tj-actions/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-30066
- Linkcisa.gov /news-events/alerts/2025/03/18/supply-chain-compromise-third-party-github-action
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.