CVE-2025-24016: Wazuh Server Deserialization of Untrusted Data Vulnerability

Is it exploited?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 10 Jun 2025, 120 days after the CVE record was published.

How likely is exploitation in the next 30 days?

93.8%

EPSS score, percentile 99.8 of all scored records

How severe?

9.9 Critical

CVSS v3.1 base score, given by the CNA

What should I do?

CISA deadline 1 Jul 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.

The CVE record links no vendor advisory, patch or mitigation.

Which versions are affected?

Affected

• >= 4.4.0, < 4.9.1

Versions by product

Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of 28 Oct 2026; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of 28 Oct 2026; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.

What to do

CISA due date for this action: 1 July 2025.

Advisories and patches

The CVE record links no vendor advisory, patch or mitigation.

Linked from CISA's catalog entry

• https://wazuh.com/blog/addressing-the-cve-2025-24016-vulnerability/
• https://github.com/wazuh/wazuh/security/advisories/GHSA-hcrc-79hj-m3qh
• https://nvd.nist.gov/vuln/detail/CVE-2025-24016

Affected products and versions

As listed in the CVE record.

Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.

About this vulnerability

Wazuh contains a deserialization of untrusted data vulnerability that allows for remote code execution on Wazuh servers.

Summary: CISA's KEV catalog, as of 28 Oct 2026.

• CISA added CVE-2025-24016 to its Known Exploited Vulnerabilities (KEV) catalog on 10 Jun 2025.
• CISA's ransomware flag for this entry is "Unknown": no evidence of ransomware use in the catalog, which is not proof of none.
• The due date CISA sets for the required action is 1 Jul 2025.
• The CVE record was published on 10 Feb 2025, 120 days before it was added to KEV.
• The CVE record carries a CVSS v3.1 base score of 9.9 (Critical), given by its CNA.
• FIRST's EPSS model puts the probability of exploitation in the next 30 days at 93.8% (percentile 99.8), as of 28 Oct 2026.
• CISA's SSVC assessment in the CVE record: exploitation active, automatable no, technical impact total.

Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of 28 Oct 2026; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of 28 Oct 2026. About the data.

Description

Remote code execution in Wazuh server

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.

Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.

Weakness

• CWE-502: Deserialization of Untrusted Data

CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record and the KEV entry.

Timeline

References

• https://github.com/wazuh/wazuh/security/advisories/GHSA-hcrc-79hj-m3qh