CVE-2025-24016 — Wazuh Server Deserialization of Untrusted Data Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (nuclei, metasploit, github)+20
- EPSS 93.8% (30-day exploitation probability)+15
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Go Github.com/wazuh/wazuh: fixed in version 4.9.1 — github.com (GitHub Security Advisories)
CISA required action CISA
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
US federal deadline: Jul 1, 2025 — passed 471 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Wazuh Wazuh, Go Github.com/wazuh/wazuh).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (insecure deserialization), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.9 | CVSS 3.1 | Critical | 3.1 | 6.0 | security-advisories@github.com via NIST National Vulnerability Database |
| 9.9 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.9 | CVSS 3.1 | Critical | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- Wazuh server remote code execution caused by an unsafe deserialization vulnerability. excellent Feb 10, 2025
- CVE-2025-24016: Wazuh Unsafe Deserialization Remote Code Execution (RCE) ★ 43 Feb 16, 2025
- Wazuh 8.4 CVE-2025-24016 ★ 8 Jul 13, 2025
- CVE-2025-24016: RCE in Wazuh server! Remote Code Execution ★ 6 Feb 20, 2025
- huseyinstif/CVE-2025-24016-Nuclei-Template ★ 4 Feb 13, 2025
- A critical RCE vulnerability has been identified in the Wazuh server due to unsafe deserialization in the wazuh-manager package. This bug affects Wazuh versions ≥ 4.4.0 and has been patched in version 4.9.1. ★ 2 Apr 21, 2025
- Detection for CVE-2025-24016 - Deserialization of Untrusted Data Vulnerability in the Wazuh software ★ 2 Jun 10, 2025
- CVE-2025-24016: RCE in Wazuh server! Remote Code Execution ★ 1 Feb 21, 2025
- celsius026/poc_CVE-2025-24016 ★ 0 Apr 15, 2025
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 93.84%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor serialized objects in requests and unexpected processes spawned by the runtime.
- Hunt retroactively in logs from before Jun 10, 2025 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · go/github.com/wazuh/wazuh
- Affected products added · wazuh/wazuh
- SSVC assessment updated
- Record published
- Affected products added · wazuh/wazuh
- CVSS changed · 9.9
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2025
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
4 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-61802 Wazuh discloses cleartext cluster key to low-privilege API users via GET /cluster/local/config Aug 27, 2026
- Critical CVE-2026-61800 Path Traversal in Wazuh Aug 27, 2026
- Medium CVE-2026-61783 Wazuh: RBAC permission-effect check in mask_sensitive_config allows low-privilege users to read cluster.key Aug 27, 2026
- High CVE-2026-54083 Wazuh: Path traversal in ip-customblock active response allows arbitrary file creation and deletion Aug 27, 2026
- Medium CVE-2026-54084 Wazuh agent enrollment NULL pointer dereference via malformed manager response Aug 27, 2026
- High CVE-2026-54085 Wazuh: Missing input validation in multiple active response scripts allows argument injection Aug 27, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-24016 is "Wazuh Server Deserialization of Untrusted Data Vulnerability", rated Critical. It affects Wazuh (Wazuh); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.9 describes technical severity. EPSS 93.84% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.