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

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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

Description quoted from the CVE record (assigned by mitre, published 2025-03-15).

Weakness: CWE-506 Embedded Malicious Code

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: partial.

On CISA KEV since
2025-03-18
US federal deadline
2025-04-08
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-00066, CNNVD-202503-1737, EUVD-2025-6565, GHSA-mrrh-fwg8-r2c3

VEDAS cluster: VEDAS:DRAGONSWOOP

Exploit Observer links 1 piece of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (1)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (3)

Vulnerability databases and vendor advisories (10)

Catalogue entries, not exploit evidence.

48 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.721
very likely to be attacked soon
VEDAS
0.981
strong exploit evidence
On CISA KEV
Yes, since 2025-03-18
Detection rule
None yet
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1CVE-2025-30066 EPSS over time2025-042026-11-01
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.9CVE-2025-30066 VEDAS over time2025-042026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
tj-actions changed-filesfrom 1 before 46Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: github_actions tj-actions/changed-files, tj-actions changed-files, сообщество_свободного_программного_обеспечения changed-files.

How to fix it

Fixed versions stated in the CVE record: 46.

CISA required action: 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.

Vendor guidance:

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

Advisories on this CVE

References

Government sources

Other references

8 more

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.