CVE-2025-15617 Wazuh GitHub Actions Workflow Exposure of Sensitive Credentials
Attackers can extract GITHUB_TOKEN from Wazuh CI artifacts to push malicious commits or alter release tags.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-15617?
CVE-2025-15617 is a high-severity vulnerability in Wazuh Wazuh, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-522
Which versions are affected by CVE-2025-15617?
It affects 1 product.
Products include Wazuh Wazuh.
How do I fix CVE-2025-15617?
No fix has been published for CVE-2025-15617 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-15617 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15617 exists.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in Wazuh Wazuh
- CVE-2025-24016 Wazuh Server Deserialization of Untrusted Data
- CVE-2024-32038 Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability
- CVE-2021-44079 Command injection in n/a
- CVE-2024-1243 Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft
- CVE-2026-61800 Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893)
Sources
Also known as GHSA-6xqr-4q5g-xc7x, GHSA-r33m-965m-8chx.