No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 31 Mar 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:wazuh:wazuh:4.12.0:*:*:*:*:*:*:* |
Tue, 31 Mar 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 30 Mar 2026 07:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wazuh
Wazuh wazuh |
|
| Vendors & Products |
Wazuh
Wazuh wazuh |
Fri, 27 Mar 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Exposure of the GITHUB_TOKEN in wazuh workflow run artifact | Wazuh GitHub Actions Workflow Exposure of Sensitive Credentials |
Fri, 27 Mar 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Exposure of the GITHUB_TOKEN in wazuh workflow run artifact | |
| Weaknesses | CWE-522 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-03-31T14:34:15.734Z
Reserved: 2026-03-27T17:55:46.750Z
Link: CVE-2025-15617
Updated: 2026-03-31T14:34:06.116Z
Status : Analyzed
Published: 2026-03-27T18:16:03.173
Modified: 2026-03-31T17:58:15.933
Link: CVE-2025-15617
No data.
OpenCVE Enrichment
Updated: 2026-03-31T20:00:55Z