CVE-2025-24016
Wazuh Server Deserialization of Untrusted Data
- Published10 Feb 2025
- Added to CISA KEV10 Jun 2025
- Remediation due1 Jul 2025
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-24016 being actively exploited?
Yes. CVE-2025-24016 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 10 Jun 2025.
How severe is CVE-2025-24016?
CVE-2025-24016 has a CVSS 3.1 base score of 9.9, rated critical. EPSS estimates a 93.8% probability of exploitation.
Which products are affected by CVE-2025-24016?
Affected products include Wazuh.
How do I fix CVE-2025-24016?
Upgrade affected software to a fixed version, for example Wazuh 4.9.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-24016 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.