⚠ Known Exploited Vulnerability (KEV) Tracker

Description

tj-actions/changed-files GitHub Action contains an embedded malicious code vulnerability that allows a remote attacker to discover secrets by reading Github Actions Workflow Logs. These secrets may include, but are not limited to, valid AWS access keys, GitHub personal access tokens (PATs), npm tokens, and private RSA keys.

Lifecycle Timeline

• 2025-03-15
  CVE published

  Entered the public CVE record.

  CVE.org →
• 2025-03-18
  Public exploit code 3 days later

  Public GitHub repository Checkmarx/Checkmarx-CVE-2025-30066-Detection-Tool — unvetted, may contain malware

  GitHub PoC →
• 2025-03-18
  First national advisory

  CISA — Supply Chain Compromise of Third-Party tj-actions/changed-files (CVE-2025-30066) and reviewdog/action-setup@v1 (CVE-2025-30154)

  CyberzSOC advisory index →
• 2025-03-18
  Added to CISA KEV

  Listed as known exploited, which starts the federal remediation clock.

  CISA KEV →
• 2025-04-08
  Federal remediation due 21 days later

  Deadline for federal civilian agencies under BOD 22-01 — now passed.

  CISA KEV
• 2025-05-10
  EPSS flags exploitation risk 32 days later

  Probability jumped from 48.2% to 59.5%. Dated to the sampled week.

  FIRST EPSS →
• not recorded
  Vendor fix published

  No dated vendor fix. Only Microsoft publishes a machine-readable release date; other vendors state a fixed version without one.

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 91 points from 2025-03-22, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 92.0% on 2026-03-28.

Published Applicability

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Research & News Coverage

No mentions found in monitored research blogs or news feeds.

Detection & Exploitation

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB and public GitHub repositories (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and are not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

CISA Assessment (Vulnrichment / SSVC)

KEV Catalog Status

Listed By

Referenced in Advisories

Weaponization Timeline — Offensive & Testing Tools

No exploit-tool sightings recorded for this CVE.

Evidence tiers are explained on the About page — a merged Metasploit module is far stronger evidence than a distro package mention.

External References

CVE.org record → NVD entry → CISA KEV catalog → FortiGuard Labs → Rapid7 AttackerKB →