Skip to main content
veriom
Menu

Explore Veriom products, resources, and account pages.

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

Patch nowHigh8.6Exploited, CISA due date 2025-04-08EPSS 72%, higher than 99% of scored CVEs

CVE-2025-30066 is a embedded malicious code in tj-actions changed-files GitHub Action, rated high (8.6 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

What it is

The product itself contains code that acts against its users.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker run their code inside your build or your running service. The damage can spread past the vulnerable component into others.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2025-03-18: it is being exploited in the wild. It can be exploited automatically, at scale. EPSS estimates a 72% chance of exploitation activity in the next 30 days, higher than 99% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2025-04-08.
  2. Upgrade tj-actions changed-files GitHub Action to 46 or later.
  3. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  4. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

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

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Build pipelines, dependencies and plugins. The flaw sits between third-party code and your build or runtime.
  • Update channels. The flaw sits between third-party code and your build or runtime.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Between third-party code and your build or runtime. An attacker who crosses it can run their code inside your build or your running service.

Questions to answer about your own systems

  • Where does tj-actions changed-files GitHub Action run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?
See how Veriom maps an architectureTake the interactive tour

Read more

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.