CI/CD secret disclosure via malicious memory dumping
Published Mar 15, 2025 · Updated Feb 26, 2026
Embedded malicious code in tj-actions changed-files 1 through 45.0.7 allows remote attackers to expose CI/CD secrets in workflow logs. The updateFeatures code downloads a Python script, reads Runner.Worker process memory through Linux /proc, double-base64-encodes secret values, and prints them. Execution on a Linux GitHub Actions runner is required, and publicly accessible logs let attackers read the exposed credentials.
Summary
What happened
Embedded malicious code in tj-actions changed-files 1 through 45.0.7 allows remote attackers to expose CI/CD secrets in workflow logs. The updateFeatures code downloads a Python script, reads Runner.Worker process memory through Linux /proc, double-base64-encodes secret values, and prints them. Execution on a Linux GitHub Actions runner is required, and publicly accessible logs let attackers read the exposed credentials.
The record
- CVE
- CVE-2025-30066
- Published
- Mar 15, 2025
- Updated
- Feb 26, 2026
- Vendor
- tj-actions
- Product
- changed-files
- Classifications
- CWE-506, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 15, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1 <46
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitHub Advisory workflow reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- CISA Known Exploited Vulnerabilities catalog listingknown exploited catalog
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo