Raw vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-15617 is a high-severity Insufficiently Protected Credentials (CWE-522) vulnerability in Wazuh Wazuh. Its CVSS base score is 8.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Remote Services (T1021); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SC-28 (Protection of Information at Rest) and SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-15617, published on 2026-03-27, is an exposure vulnerability (CWE-522) in Wazuh version 4.12.0. The issue resides in GitHub Actions workflow artifacts, which inadvertently allow attackers to extract the GITHUB_TOKEN from uploaded artifacts. This token exposure enables unauthorized access within the workflow's limited time window.
The vulnerability can be exploited remotely (AV:N) by unauthenticated attackers (PR:N) with no user interaction (UI:N), though it requires high attack complexity (AC:H). Successful exploitation grants the GITHUB_TOKEN's permissions, allowing actions such as pushing malicious commits or altering release tags in the Wazuh repository. The CVSS v3.1 base score is 6.5 (C:N/I:H/A:L/S:U), reflecting moderate integrity and low availability impact.
Advisories detailing mitigation are available from the Wazuh GitHub security page at https://github.com/wazuh/wazuh/security/advisories/GHSA-6xqr-4q5g-xc7x and VulnCheck at https://www.vulncheck.com/advisories/exposure-of-the-github-token-in-wazuh-workflow-run-artifact.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-209105
Vulnerability Data
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…
more
malicious commits or altering release tags.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
V11.3.3
Mitigating Controls (NIST 800-53 r5) AI
Protection of information at rest requires encryption or equivalent safeguards for stored credentials.
Transmission confidentiality and integrity enforcement stops credentials from being sent in plaintext or without protection.
Authenticator management requires secure generation, storage, and distribution of credentials, directly stopping insecure methods.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Credential management practices directly reduce insecure storage/transmission but do not guarantee encryption or transport protection.
Authentication policies can enforce stronger credential handling yet address only verification, not storage or transit protection.
Protecting identity assertions covers conveyance of credentials but is narrower than full credential lifecycle protection.
Encrypting data-at-rest fully prevents insecure credential storage while only partially satisfying the broader data-protection outcome.
Encrypting data-in-transit fully prevents interception of credentials in motion while only partially satisfying the broader data-protection outcome.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Acceptable-use expectations that cover protection of credentials and information assets throughout their lifecycle discourage practices that expose or mishandle authentication material.
Requiring protected storage, transmission, and non-display of passwords prevents credentials from being stored or sent in clear text where they can be harvested by unauthorized actors.
Contractual clauses that survive termination help ensure that credentials and other secrets are not retained or misused after employment ends.
Regular reminders about password security and personal accountability make users less likely to store or transmit credentials in cleartext or other unprotected forms.
By requiring signatories to protect credentials and other authentication material under the same confidentiality terms, the control discourages the mishandling or exposure of credentials that could lead to unauthorized account access.
Requiring logical controls such as passwords or PINs on idle devices and the use of remote lockout mechanisms protects credentials and other sensitive material from offline extraction.