Skip to content
Fencer Vulns
critical 9.9

CVE-2025-24016 kev in the critical feed json

Remote code execution in Wazuh server

published 2025-02-10 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-3595 , GHSA-hcrc-79hj-m3qh , GO-2025-3459

cvss
9.9
version 3.1, CNA
cisa kev
Exploited
added 2025-06-10
epss
93.8%
EPSS 93.8% chance of exploitation in 30 days, percentile 99.8%
public exploits
1
Metasploit, plus a Nuclei check

Summary

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.

Patch / 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.

  • go github.com/wazuh/wazuh 4.9.1, 4.9.1+incompatible
  • wazuh wazuh 4.9.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250312T181707-1.1

opensuse advisories openSUSE-SU-2025:14889-1

Timeline

  1. First public exploit (Metasploit exploit/linux/http/wazuh_auth_rce_cve_2025_24016)
  2. Published
  3. Added to CISA KEV
  4. CISA patch deadline
  5. CISA SSVC: exploitation active

Known exploited

Added
17 mo ago
Patch by
2025-07-01 (16 mo ago)
Ransomware
Not known
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.
Vendor, product
Wazuh, Wazuh Server
CISA name
Wazuh Server Deserialization of Untrusted Data Vulnerability

ATT&CK techniques

How it is exploited and what it leads to, in MITRE ATT&CK terms.

  • T1078 Valid Accounts exploitation
  • T1059 Command and Scripting Interpreter primary impact
  • T1203 Exploitation for Client Execution secondary impact

kev release 2025-07-28, att&ck v16.1. KEV to ATT&CK mappings by the MITRE Center for Threat-Informed Defense (Mappings Explorer, Apache-2.0). © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. Terms of use

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
14 mo ago

Exploit prediction

93.84% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H/E:H

Affected packages

ecosystem package affected fixed in
go github.com/wazuh/wazuh
>=4.4.0, <4.9.1
>=4.4.0+incompatible, <4.9.1+incompatible
4.9.1
4.9.1+incompatible

Affected products

  • wazuh wazuh

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.