Repository compromise via token-bearing workflow artifact
Published Apr 21, 2025 · Updated Apr 22, 2025
Credential exposure in Adept 2.7 allows remote attackers to obtain a GitHub Actions token from a published workflow artifact. The remoteBuild.yml job zipped the macOS staging directory without excluding nested .git data, so actions/upload-artifact published .git/config with the run token. Exploitation requires monitoring an active workflow run and downloading the artifact before the short-lived token expires; the token grants repository write access.
Summary
What happened
Credential exposure in Adept 2.7 allows remote attackers to obtain a GitHub Actions token from a published workflow artifact. The remoteBuild.yml job zipped the macOS staging directory without excluding nested .git data, so actions/upload-artifact published .git/config with the run token. Exploitation requires monitoring an active workflow run and downloading the artifact before the short-lived token expires; the token grants repository write access.
The record
- CVE
- CVE-2025-32958
- Published
- Apr 21, 2025
- Updated
- Apr 22, 2025
- Vendor
- AdeptLanguage
- Product
- Adept
- Classifications
- CWE-200, CWE-522, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2025CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record 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=< a1a41b7
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.
Weakness, pattern, technique
Public exploit references
- Workflow artifact token extraction proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
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