CVE-2025-24016 Wazuh Server Deserialization of Untrusted Data
An unsafe deserialization flaw in Wazuh server allows attackers with API access to execute arbitrary Python code remotely.
- Exploited in the wild
- Since 10 Jun 2025
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-24016?
CVE-2025-24016 is a critical unsafe deserialization vulnerability in Wazuh Wazuh, published on 10 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-502
Which versions are affected by CVE-2025-24016?
3 open source packages ship an affected version, including github.com/wazuh/wazuh. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/wazuh/wazuh Go | From 4.4.0 | 4.9.1 |
github.com/wazuh/wazuh Go | From 4.4.0 | 4.9.1 |
github.com/wazuh/wazuh Go | From 4.4.0+incompatible | 4.9.1+incompatible |
Products include Wazuh Wazuh.
How do I fix CVE-2025-24016?
Upgrade github.com/wazuh/wazuh to a fixed version for your release line: 4.9.1 or 4.9.1+incompatible. US federal agencies must fix it by 1 Jul 2025.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2025-24016 being exploited?
Yes. Attackers have exploited CVE-2025-24016 in the wild since at least 10 Jun 2025.
Public exploit code: 1 Metasploit module, 1 Nuclei template and 8 proofs of concept on GitHub.
Other vulnerabilities in Wazuh Wazuh
- CVE-2024-32038 Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability
- CVE-2021-44079 Command injection in n/a
- CVE-2024-1243 Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft
- CVE-2026-61800 Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893)
- CVE-2026-48024 Wazuh: merged-file header path traversal in cluster sync allows arbitrary file write under WAZUH_PATH in Wazuh manager
Sources
Also known as GHSA-hcrc-79hj-m3qh, GO-2025-3459.