CVE-2025-15617
Wazuh GitHub Actions Workflow Exposure of Sensitive Credentials
Wazuh version 4.12.0 contains an exposure vulnerability in GitHub Actions workflow artifacts that allows attackers to extract the GITHUB_TOKEN from uploaded artifacts. Attackers can use the exposed token within a limited time window to perform unauthorized actions such as pushing malicious commits or altering release tags.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Wazuh (GitHub Actions) Wazuh |
4.12.0 (affected, semver)
Other versions: unaffected |
CNA: VulnCheck |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 8.3 high |
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N | CNA: VulnCheck |
| 3.1 / 6.5 medium |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L | CNA: VulnCheck |
Exploit evidence
- https://github.com/wazuh/wazuh/security/advisories/GHSA-6xqr-4q5g-xc7x
exploit · ADP: CISA-ADP
References
- https://github.com/wazuh/wazuh/security/advisories/GHSA-6xqr-4q5g-xc7xCNA: VulnCheck · vendor-advisory
- https://www.vulncheck.com/advisories/exposure-of-the-github-token-in-wazuh-workflow-run-artifactCNA: VulnCheck · third-party-advisory
- https://github.com/wazuh/wazuh/security/advisories/GHSA-6xqr-4q5g-xc7xADP: CISA-ADP · exploit
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.