Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-15617: CWE-522 Insufficiently Protected Credentials in Wazuh Wazuh (GitHub Actions)

0
Medium
VulnerabilityCVE-2025-15617cvecve-2025-15617cwe-522
Published: Fri Mar 27 2026 (03/27/2026, 18:04:13 UTC)
Source: CVE Database V5
Vendor/Project: Wazuh
Product: 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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/04/2026, 10:54:02 UTC

Technical Analysis

CVE-2025-15617 is a medium severity vulnerability affecting Wazuh version 4.12.0. It involves insufficient protection of credentials in GitHub Actions workflows, specifically the exposure of the GITHUB_TOKEN through workflow artifacts. Attackers who access these artifacts can extract the token and use it to perform unauthorized repository actions such as pushing commits or modifying release tags. The vulnerability is identified as CWE-522 and has a CVSS 4.0 score of 6.3, reflecting network attack vector with high attack complexity and high impact on integrity and availability. No patch or official fix information is provided in the available data.

Potential Impact

The vulnerability allows attackers to extract the GITHUB_TOKEN from GitHub Actions workflow artifacts, enabling unauthorized actions within the affected repository. This can lead to malicious commits or unauthorized changes to release tags, potentially compromising the integrity of the codebase and release process. The impact is limited by the token's validity window and the scope of permissions granted to the token. There are no known exploits in the wild currently.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider restricting permissions of the GITHUB_TOKEN, avoid uploading sensitive tokens in workflow artifacts, and review GitHub Actions workflows for exposure risks. Monitor official Wazuh and GitHub advisories for updates and apply patches promptly once released.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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: 3/27/2026, 6:14:47 PM

Last enriched: 4/4/2026, 10:54:02 AM

Last updated: 5/11/2026, 5:20:09 AM

Views: 73

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses