Repository compromise via token-bearing workflow artifacts
Published Mar 27, 2026 · Updated Mar 27, 2026
Credential exposure in Wazuh 4.12.0 GitHub Actions artifacts allows attackers to obtain a workflow run's GITHUB_TOKEN. The 4_testintegration_fim-tier-0-1-win.yml workflow uploads the current directory, packaging .git/config where GitHub stored the token. Remote attackers must monitor the workflow and act within the short token-validity window; successful reuse permits malicious commits or release-tag changes.
Summary
What happened
Credential exposure in Wazuh 4.12.0 GitHub Actions artifacts allows attackers to obtain a workflow run's GITHUB_TOKEN. The 4_testintegration_fim-tier-0-1-win.yml workflow uploads the current directory, packaging .git/config where GitHub stored the token. Remote attackers must monitor the workflow and act within the short token-validity window; successful reuse permits malicious commits or release-tag changes.
The record
- CVE
- CVE-2025-15617
- Published
- Mar 27, 2026
- Updated
- Mar 27, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-522, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2026CVE publishedPublication date reported by the CVE source.
- Mar 27, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Vendor advisory proof-of-concept procedureproof 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