Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Evidence dossier
CVE-2025-24016
Remote code execution in Wazuh server
gen-56ccdaf9Normalized restatement
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.
- State
- PUBLISHED
- Published
- Feb 10, 2025
- Updated
- Feb 26, 2026
- Evidence coverage
- 85%
2026-07-18 · v2026.06.15 · percentile 99.8%
Distinct CVSS assessments remain side by side; none are averaged.
Source comparison
Who said what
Remote code execution in Wazuh server
Wazuh Server Deserialization of Untrusted Data Vulnerability
Probability 0.930270000000; percentile 0.998190000000
Applicability
Cited product scope
[{"status": "affected", "version": ">= 4.4.0, < 4.9.1"}]unknowncpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*; start including 4.4.0; end excluding 4.9.1supportedAssessments
CVSS by origin
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:HCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:HLimitations and unknowns
- KEV membership is authoritative for the catalog, not proof of exposure in any environment.
- EPSS is a dated model probability and not an individual-environment prediction.
- Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
- NVD-carried upstream facts remain derivative and are not independent corroboration.
- Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
- NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
- Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
- Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.