How severe is CVE-2025-24016?

CVE-2025-24016 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-24016?

CVE-2025-24016 affects the following packages: github.com/wazuh/wazuh (Go). Ecosystems affected: Go.

How do I fix CVE-2025-24016?

Update github.com/wazuh/wazuh to version 4.9.1 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2025-24016 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2025-24016, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-24016?

CVE-2025-24016 has an EPSS (Exploit Prediction Scoring System) score of 93.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2025-24016 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-24016 (Wazuh Server Deserialization of Untrusted Data Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-06-10. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-07-01. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-24016?

CVE-2025-24016 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2025-24016?

A Nuclei detection template exists for CVE-2025-24016, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2025-24016 published, and has it been updated?

CVE-2025-24016 was published on February 10, 2025 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2025-06-10 — agencies required to remediate by 2025-07-01

🐹 Go

CVE-2025-24016

CRITICAL

Remote code execution in Wazuh server

Also known asGHSA-hcrc-79hj-m3qhGO-2025-3459

Published

Feb 10, 2025

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

93.9%probability of exploitation in next 30 days

Very High Risk100th percentile+0.36%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/wazuh/wazuh

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/wazuh/wazuh`	≥ 4.4.0&&< 4.9.1	4.9.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

0xjessie21/CVE-2025-24016

CVE-2025-24016: Wazuh Unsafe Deserialization Remote Code Execution (RCE)

⭐ 43🍴 6Apr 2026

guinea-offensive-security/Wazuh-RCE

Wazuh 8.4 CVE-2025-24016

⭐ 8🍴 2Apr 2026

MuhammadWaseem29/CVE-2025-24016

CVE-2025-24016: RCE in Wazuh server! Remote Code Execution

⭐ 5🍴 0Feb 2026

huseyinstif/CVE-2025-24016-Nuclei-Template

⭐ 4🍴 1Jan 2026

Frequently Asked Questions

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 anyb

O3 Security · Impact-Aware SCA

Is CVE-2025-24016 in your stack?

O3 detects CVE-2025-24016 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works