CVE-2025-15617: CWE-522 Insufficiently Protected Credentials in Wazuh Wazuh (GitHub Actions)
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.
AI Analysis
Technical Summary
CVE-2025-15617 is a high-severity vulnerability affecting Wazuh version 4.12.0 related to insufficient protection of credentials (CWE-522) in GitHub Actions workflow artifacts. Specifically, the GITHUB_TOKEN used in the workflow is exposed through uploaded artifacts, enabling attackers to extract it. With this token, attackers can perform unauthorized actions such as pushing malicious commits or altering release tags within a limited time window. The vulnerability has a CVSS 4.0 base score of 8.3, indicating a significant risk if exploited. No patch or official remediation guidance is currently provided, and the product is not a cloud service, so remediation depends on vendor updates or user action.
Potential Impact
The exposed GITHUB_TOKEN can be used by attackers to perform unauthorized actions in the affected repository, including pushing malicious commits and modifying release tags. This can lead to code integrity compromise and potential supply chain risks. The vulnerability requires network access and has a high attack complexity, but no privileges or user interaction are needed. The impact is limited by the token's validity window but remains significant due to the ability to alter source code and releases.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid using Wazuh version 4.12.0 in environments where GitHub Actions artifacts might be exposed. Consider restricting artifact access and rotating tokens frequently. Monitor official Wazuh channels for updates and apply patches promptly once released.
CVE-2025-15617: CWE-522 Insufficiently Protected Credentials in Wazuh Wazuh (GitHub Actions)
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.
CVSS v4.0
Score 8.3high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-15617 is a high-severity vulnerability affecting Wazuh version 4.12.0 related to insufficient protection of credentials (CWE-522) in GitHub Actions workflow artifacts. Specifically, the GITHUB_TOKEN used in the workflow is exposed through uploaded artifacts, enabling attackers to extract it. With this token, attackers can perform unauthorized actions such as pushing malicious commits or altering release tags within a limited time window. The vulnerability has a CVSS 4.0 base score of 8.3, indicating a significant risk if exploited. No patch or official remediation guidance is currently provided, and the product is not a cloud service, so remediation depends on vendor updates or user action.
Potential Impact
The exposed GITHUB_TOKEN can be used by attackers to perform unauthorized actions in the affected repository, including pushing malicious commits and modifying release tags. This can lead to code integrity compromise and potential supply chain risks. The vulnerability requires network access and has a high attack complexity, but no privileges or user interaction are needed. The impact is limited by the token's validity window but remains significant due to the ability to alter source code and releases.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid using Wazuh version 4.12.0 in environments where GitHub Actions artifacts might be exposed. Consider restricting artifact access and rotating tokens frequently. Monitor official Wazuh channels for updates and apply patches promptly once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-03-27T17:55:46.750Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69c6c9173c064ed76fdf3893
Added to database: 03/27/2026, 18:14:47 UTC
Last enriched: 05/13/2026, 02:09:00 UTC
Last updated: 07/31/2026, 19:22:53 UTC
Views: 159
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.