Vulnerability record

CVE-2025-30066

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker snapshot: Aug 8, 2026.

What it is

Reported

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. Source description excerpt; complete tracked detail loads below.

NVD published: Mar 15, 2025 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What is affected

Reported

tj-actions — changed-files GitHub Action. Product-level identification only; no affected-version conclusion is available from this field.

NVD published: Mar 15, 2025 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Urgency and basis

Reported

Act · 462.3

Tracker decision tier from the evidence detailed below · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Exploitation evidence

Reported

kev-listed · CISA KEV · VulnCheck KEV · ENISA exploited-vulnerability catalog

Active since: Mar 18, 2025 · CISA KEV added: Mar 18, 2025 · VulnCheck KEV added: Mar 14, 2025 · ENISA added: Mar 18, 2025 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What to do

Reported

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.

Tracked source remediation field · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Evidence detail

Loading the full tracker evidence record…