Remote code execution in Wazuh server
Affects Wazuh server (wazuh-manager) versions from 4.4.0 up to but not including 4.9.1. The vendor-set CVSS score is 9.9 (critical). Fixed in 4.9.1.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 4.9.1, 4.9.1+incompatible
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Wazuh, an open source threat detection and response platform, is affected, specifically its server component in versions before 4.9.1. An attacker who can send crafted requests, such as someone with API access or a compromised cluster node or agent, could run arbitrary code on the Wazuh server.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 4.4.0 and prior to version 4.9.1, an unsafe deserialization vulnerability allows for remote code execution on Wazuh servers. DistributedAPI parameters are a serialized as JSON and deserialized using `as_wazuh_object` (in `framework/wazuh/core/cluster/common.py`). If an attacker manages to inject an unsanitized dictionary in DAPI request/response, they can forge an unhandled exception (`__unhandled_exc__`) to evaluate arbitrary python code. The vulnerability can be triggered by anybody with API access (compromised dashboard or Wazuh servers in the cluster) or, in certain configurations, even by a compromised agent. Version 4.9.1 contains a fix.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- wazuh wazuh
From 4.4.0 · fixed in 4.9.1
- github.com/wazuh/wazuhGo
From 4.4.0 · fixed in 4.9.1
- github.com/wazuh/wazuhGo
From 4.4.0+incompatible · fixed in 4.9.1+incompatible
References 1
GitHub · wazuh/wazuh
Questions about CVE-2025-24016
What does this mean?
This bug allows remote code execution on Wazuh servers, meaning code run by an attacker could execute on the server host. The advisory describes the impact as remote code execution on the Wazuh server.Source: github.com
Am I affected, and how do I check?
Wazuh server (wazuh-manager) versions from 4.4.0 up to but not including 4.9.1 are in the affected range. The advisory says the attack needs API access, such as through a compromised dashboard or a Wazuh server in the cluster, and that the agent-based path requires certain configurations.Source: github.com
What should I do about it?
Upgrade the Wazuh server to version 4.9.1 or later, which is the patched release named in the advisory.Source: github.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-06-10, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data