CVE-2025-24016: Wazuh server unsafe deserialization remote code execution

Exploited in the wild Critical 9.9 EPSS 93.8%

The Wazuh server deserializes DistributedAPI parameters with as_wazuh_object, and a forged __unhandled_exc__ object makes it evaluate arbitrary Python, giving remote code execution on the master server. Anyone with server API access can trigger it (for example via the run_as endpoint), and in some setups a compromised agent can too. Fixed in 4.9.1 (October 2024); after botnet activity was reported, CISA added it to KEV on 10 June 2025.

CVE-2025-24016CVE identifier
9.9CVSS 3.1 base score (critical)
2025-06-10added to CISA's exploited list (US federal deadline 2025-07-01)
93.8%EPSS: chance of exploitation in the next 30 days (higher than 100% of CVEs)
2025-02-10published

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

Check whether you run the affected software and which version (commands below).
Install the fixed version for your system: see “Patch it” below.
Restart wazuh-manager on every server node; follow Wazuh's upgrade guide for the indexer and dashboard.
If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.
Because this flaw is being exploited, also check the server for signs of compromise.

Affected and fixed versions

Affected:

Wazuh 4.4.0 before 4.9.1

Fixed in:

Wazuh 4.9.1

Am I affected?

/var/ossec/bin/wazuh-control info
dpkg -l wazuh-manager | grep ^ii; rpm -q wazuh-manager

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Debian

sudo apt-get update
sudo apt-get install wazuh-manager
sudo systemctl restart wazuh-manager

Ubuntu

sudo apt-get update
sudo apt-get install wazuh-manager
sudo systemctl restart wazuh-manager

RHEL, AlmaLinux, Rocky, Oracle

sudo yum upgrade wazuh-manager
sudo systemctl restart wazuh-manager

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

If you cannot patch yet

Do not expose the Wazuh server API (port 55000) to the internet (Wazuh).
Change default credentials such as the wazuh-wui API user.

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.

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

Sources

Page generated automatically from official sources on 2026-11-03 18:05 UTC and reviewed by an editor. Always confirm with your vendor's advisory.