Security readout for executives and security teams
Plain-English summary
CVE-2025-24016 lets an attacker with Wazuh API access, or certain compromised cluster/agent positions, execute code on Wazuh servers. Because Wazuh is a security monitoring platform, compromise can affect detection, response, and operational trust. CISA KEV listing indicates known exploitation has occurred.
Executive priority
Treat this as urgent for any Wazuh deployment below 4.9.1. The affected system is a security control, the impact includes remote code execution, and CISA KEV confirms exploitation. Prioritize upgrade and access review before routine backlog work.
Technical view
Wazuh versions 4.4.0 through before 4.9.1 deserialize DistributedAPI JSON parameters with as_wazuh_object. An attacker who injects an unsanitized dictionary into DAPI traffic can forge an unhandled exception marker that evaluates arbitrary Python code. The issue is CWE-502 unsafe deserialization and has CVSS 9.9.
Likely exposure
Organizations running Wazuh server versions >= 4.4.0 and < 4.9.1 are exposed. Risk is highest where API access, dashboards, clustered Wazuh servers, or agent-to-cluster configurations could be abused after credential or node compromise.
Exploitation context
The CVE record says exploitation requires API access, a compromised dashboard, a compromised Wazuh cluster server, or in certain configurations a compromised agent. CISA KEV confirms known exploitation, but the provided sources do not describe public exploit tooling or campaign details.
Researcher notes
Source evidence is strong for affected versions, root cause, trigger conditions, CVSS, CWE, and fixed version. Evidence is incomplete on exploit prevalence, specific attacker procedures, and non-upgrade mitigations. Avoid assuming agent-based triggering unless the deployment matches the cited certain configurations.
Mitigation direction
- Upgrade affected Wazuh servers to version 4.9.1 or later.
- Review Wazuh vendor advisory for current remediation guidance.
- Restrict Wazuh API access to trusted administrative paths only.
- Review dashboard, cluster server, and agent trust boundaries.
- Monitor Wazuh servers for unexpected code execution or service anomalies.
Validation and detection
- Inventory all Wazuh server versions across clusters.
- Confirm no server is running versions 4.4.0 through 4.9.0.
- Identify who and what can reach the Wazuh API.
- Review cluster and dashboard compromise paths relevant to DAPI traffic.
- Check CISA KEV tracking for operational deadlines and updates.
Public sources used
Michael Williams reviewed this cited source version on .
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-24016 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H3.16Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wazuh/wazuh/security/advisories/GHSA-hcrc-79hj-m3qhCVE reference · x_refsource_CONFIRM
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24016CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.