Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:NSummary
CVE-2025-30066 is a high-severity Embedded Malicious Code (CWE-506) vulnerability in Tj-Actions Changed-Files. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Embedded Payloads (T1027.009); ranked in the top 0.7% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SC-44 (Detonation Chambers) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability CVE-2025-30066 affects the tj-actions/changed-files GitHub Action in versions before 46. It enables remote attackers to discover secrets by reading workflow action logs. The issue stems from a supply-chain compromise in which tags v1 through v45.0.7 were altered on 2025-03-14 and 2025-03-15 to reference commit 0e58ed8 containing malicious updateFeatures code, classified under CWE-506.
Attackers with no authentication or user interaction can exploit the flaw over the network, achieving high-impact confidentiality breaches by extracting secrets that appear in GitHub Actions logs. The CVSS 8.6 score reflects the change in scope and the absence of required privileges or user interaction.
Public references, including GitGuardian analysis and GitHub security-hardening guidance, recommend pinning actions to specific commit hashes rather than version tags, reviewing workflow logs for unexpected changes, and regenerating any secrets that may have been exposed. The associated EPSS score remains elevated near 0.92, indicating sustained exploitation interest following disclosure of the tag-poisoning incident.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6565
Vulnerability Data
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…
more
malicious updateFeatures code.)
- CWE(s)
- KEV Date Added
- 18 March 2025
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover embedded malicious code before release.
Detonation chambers can reveal embedded malicious code through controlled execution analysis.
Integrity verification tools directly detect unauthorized or malicious code insertions.
Tamper-resistance and detection mechanisms identify malicious code introduced via the supply chain.
Component authenticity requirements reduce the chance malicious code is embedded by developers or suppliers.
Component authenticity controls stop introduction of malicious or counterfeit code into the product.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Assessing authenticity and integrity before acquisition catches embedded malicious code.
Secure SDLC practices directly prevent introduction of malicious code during development.
Due diligence prior to supplier relationships helps avoid sources of embedded malicious code.
Supplier risk assessment reduces likelihood of receiving products containing malicious code.
Pre-acquisition assessment of critical suppliers mitigates risk of malicious code in procured software.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring suppliers to furnish component lists, attestations, and cryptographic verification of delivered artefacts makes it harder for an attacker to embed hidden malicious code that would otherwise go undetected through the supply chain.
Checks that executed code has not been tampered with and monitoring for malware-associated activity reduce the likelihood that hidden malicious code remains active.
Banning unapproved or unknown software and requiring testing plus authorization reduces the chance that hidden malicious code will be introduced into production environments.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 9 (1 rule)
- V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-506
RHEL 9 (1 rule)
- V-258078 RHEL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-506