CVE-2025-24016: Wazuh Server Deserialization of Untrusted Data
Wazuh Server · listed in the CISA catalog of actively exploited vulnerabilities since 2025-06-10.
- CVSS v3.1 (CVE record)
- 9.9
- critical
- EPSS (exploit probability, 30 days)
- 95%
- higher than 99.8% of all CVEs
- Added to CISA KEV
- 2025-06-10
- US federal due date 2025-07-01
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-24016 explained
CVE-2025-24016 is an unsafe deserialization vulnerability in Wazuh Server that allows remote code execution on Wazuh servers. It affects how DistributedAPI parameters are deserialized. CISA lists it as known to be exploited, so affected deployments of this security monitoring platform should be treated as a priority.
Impact
An attacker with API access can run arbitrary Python code on Wazuh servers. Such access could come from a compromised dashboard or Wazuh servers in the cluster. In certain configurations, a compromised agent can also trigger it. The attack works over the network with low complexity and low privileges, and needs no user interaction. CISA rates the technical impact as total but not automatable. Attackers are known to exploit it.
Who is affected
The CVE record lists wazuh versions ≥ 4.4.0 and < 4.9.1 as affected, meaning versions from 4.4.0 up to but not including 4.9.1. The structured fixedIn field of the CVE record names no fixed version. However, the record's description states that version 4.9.1 contains a fix.
Written with AI from the data on this page and checked against it automatically.
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.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- wazuhAffectedFixed in
- ≥ 4.4.0
- < 4.9.1
not stated
| Product | Affected | Fixed in |
|---|---|---|
| wazuh |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: github.com/wazuh/wazuh/security/advisories/GHSA-hcrc-79hj…
- CISA's deadline for US federal agencies: 2025-07-01 (passed) – a useful benchmark for everyone else, too.
What to do
- Upgrade all Wazuh servers in the cluster to
4.9.1or later, as the CVE description states this version contains the fix. - Follow the Wazuh vendor advisory and apply its mitigations, as CISA's required action directs.
- Restrict access to the Wazuh API and dashboard to trusted administrative networks only.
- Review Wazuh servers, dashboards and agents for signs of compromise, since attackers are known to exploit this flaw.
- If mitigations cannot be applied, follow CISA's guidance to discontinue use of the affected product.
The structured fixedIn field names no fixed version, although the description states 4.9.1 contains a fix. Confirm the fixed release in the vendor advisory. Until you can upgrade, apply the vendor's mitigations, limit API and dashboard access, and follow CISA's required action, which includes discontinuing use if mitigations are unavailable.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-502 Deserialization of Untrusted Data
Questions about CVE-2025-24016
- Who can trigger this vulnerability?
- Anyone with API access, such as a compromised dashboard or a Wazuh server in the cluster. In certain configurations, a compromised agent can also trigger it.
- Is CVE-2025-24016 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-06-10, with a US federal due date of 2025-07-01. Ransomware use is listed as unknown.
- Which version should we upgrade to?
- The CVE description states that version
4.9.1contains a fix. Affected versions are from4.4.0up to but not including4.9.1.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.