CVE-2025-15617: Wazuh version 4.12.0 contains an exposure vulnerability in GitHub Actions workflow artifacts that allows attac

This week

MEDIUM 6.5REMOTEDOWNGRADE

CVE-2025-15617 is a medium-severity flaw (CVSS 6.5) affecting wazuh. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-522
Published	2026-03-27
Last modified	2026-10-07

Publisher (CNA): VulnCheck · Vendor: wazuh

Last updated 2026-10-07 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-27 18:16 UTCPublished CVE record published
2026-10-07 09:10 UTCUpdated Record last modified

wazuh wazuh DOWNGRADE

Affected: 4.12.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.12.0

1. Check installed version

apt-cache policy wazuh || rpm -q wazuh || wazuh --version

2. No fixed release: DOWNGRADE to a release before 4.12.0 (Debian / Ubuntu)

apt-cache madison wazuh sudo apt install wazuh=<VERSION_BEFORE_4.12.0> sudo apt-mark hold wazuh

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list wazuh sudo dnf downgrade wazuh-<VERSION_BEFORE_4.12.0> sudo dnf versionlock add wazuh

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-15617?

wazuh: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-15617 being exploited?

CVE-2025-15617 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-15617 affect?

CVE-2025-15617 affects wazuh. Severity is medium (CVSS 6.5). 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 perf

How urgent is CVE-2025-15617?

Priority 41/100. Public exploit reference; Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities · Wazuh vulnerabilities

Related CVEs

CVE-2026-44252 HIGH 8.8 UPGRADE Wazuh is a free and open source platform used for threat prevention, detection, and response
CVE-2026-46343 HIGH 7.2 UPGRADE Wazuh is a free and open source platform used for threat prevention, detection, and response
CVE-2026-44253 MEDIUM 4.9 UPGRADE Wazuh is a free and open source platform used for threat prevention, detection, and response
CVE-2026-44254 MEDIUM 5.3 UPGRADE Wazuh is a free and open source platform used for threat prevention, detection, and response
CVE-2026-32983 MEDIUM 5.8 UPGRADE Wazuh Manager authd service in wazuh-manager packages through version 4.7.3 contains an improper restriction o

References

← Back to latest CVEs