Wazuh up to 4.9.0 common.py as_wazuh_object deserialization

Summaryinfo

A vulnerability identified as critical has been detected in Wazuh up to 4.9.0. Impacted is the function as_wazuh_object of the file framework/wazuh/core/cluster/common.py. The manipulation leads to deserialization. This vulnerability is uniquely identified as CVE-2025-24016. The attack is possible to be carried out remotely. Moreover, an exploit is present. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Wazuh up to 4.9.0. This issue affects the function as_wazuh_object of the file framework/wazuh/core/cluster/common.py. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-24016 since 01/16/2025. The exploitation is known to be easy. The attack may be initiated remotely. Technical details as well as a exploit are known.

It is declared as attacked. The vulnerability scanner Nessus provides a plugin with the ID 235712 (Wazuh Server 4.4.0 < 4.9.1 RCE), which helps to determine the existence of the flaw in a target environment. The CISA Known Exploited Vulnerabilities Catalog lists this issue since 06/10/2025 with a due date of 07/01/2025:

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Upgrading to version 4.9.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (235712). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Wazuh

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4
• 4.5
• 4.6
• 4.7
• 4.8
• 4.9.0

Website

• Product: https://github.com/wazuh/wazuh/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion