dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 1 Jul 2025.
WazuhApplication

CVE-2025-24016

CRITICAL · 9.9 CVSS v3.1 Published 2025-02-10
Fix available
A fix is available. Upgrade to 4.9.1 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Wazuh versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI (framework/wazuh/core/cluster/common.py). The `as_wazuh_object` function deserializes JSON parameters without proper sanitization, allowing attackers with API access to inject a malicious dictionary containing a forged `__unhandled_exc__` attribute that triggers arbitrary Python code execution on the server.

MitigationUpgrade Wazuh to version 4.9.1 or later to patch the unsafe deserialization vulnerability. Additionally, restrict API access, rotate credentials if compromise is suspected, and monitor DAPI traffic for anomalies.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WazuhApplication
Affected:>= 4.4.0, < 4.9.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Wazuh version
    Run `wazuh-control info` or check `/etc/ossec-init.conf` to obtain the installed version number
    Affected if The version is 4.4.0 through 4.9.0 (specifically >= 4.4.0 and < 4.9.1)
  2. Verify the vulnerable file exists
    Confirm the presence of framework/wazuh/core/cluster/common.py in the Wazuh installation directory
    Affected if The file exists and the Wazuh version falls within the affected range
  3. Confirm Wazuh API is accessible
    Check if the Wazuh API service is running and network-accessible (port 55000 by default). Verify with `systemctl status wazuh-api` or by attempting a local connection
    Affected if The API is exposed and the installed version is within the affected range
  4. Check if cluster mode is enabled
    Inspect the Wazuh cluster configuration in /var/ossec/etc/ossec.conf or check cluster status using `wazuh-control list`
    Affected if Cluster functionality is enabled and the version is vulnerable

You are affected if Wazuh version is 4.4.0 through 4.9.0 and the Wazuh API/cluster service is running and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.9.1 or later
Fixed in 4.9.1
Interim mitigation

Upgrade Wazuh to version 4.9.1 or later to patch the unsafe deserialization vulnerability. Additionally, restrict API access, rotate credentials if compromise is suspected, and monitor DAPI traffic for anomalies.

Recommended fix High confidence

4.9.1

  1. 1. Back up your current Wazuh configuration and data
  2. 2. Stop all Wazuh services (wazuh-manager, wazuh-api, wazuh-dashboard if applicable)
  3. 3. Upgrade Wazuh to version 4.9.1 or later
  4. 4. Verify the upgrade was successful by checking the Wazuh version (wazuh-control info or API endpoint)
  5. 5. Restart Wazuh services
Caveat Review Wazuh 4.9.1 release notes for any breaking changes from your current minor version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wazuh Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24016 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24016 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data