CVE-2025-24016: Wazuh Server Deserialization of Untrusted Data Vulnerability

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Yes, if you run Wazuh Wazuh Server. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2025-06-10, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2025-07-01; treat that as the outer limit, not the target.
• EPSS 93.8%, percentile 99.8: FIRST’s model estimates a 93.8% chance of exploitation activity in the next 30 days, higher than 99.8% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Needs an account (low (any account)). Exposure depends on who can log in.
• Only applies if your dependency tree includes github.com/wazuh/wazuh (Go) >= 4.4.0, < 4.9.1, fixed in 4.9.1. Check your lockfile, including transitive dependencies.

What it is

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 aswazuhobject (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 (unhandledexc) 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.

From the GitHub advisory

Summary An unsafe deserialization vulnerability allows for remote code execution on Wazuh servers. 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.

Details DistributedAPI parameters are a serialized as JSON and deserialized using aswazuhobject (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 (unhandledexc) to evaluate arbitrary python code.

Using the server API, it quite easy to trigger. For example, using the runas endpoint (implemented by runaslogin in api/api/controllers/securitycontroller.py): the authcontext argument is completely controlled by the attacker, and is forwarded to the master server to handle. By sending a malicious runas request to a worker server, it is possible to execute code on the master server.

It is also possible to exploit the bug as a compromised agent, in certain configurations. A compromised agent can respond to a getconfig request with a malicious JSON object (containing a serialized unhandled exception). If the getconfig request was caused because of a server API request to /agents/{agentid}/config/{component}/{configuration} (api.controllers.agentcontroller.getagentconfig), and the agent is managed by a server other than the one that received the server API request, the unsafe deserialization will occur on the server that received the original server API request.

It is likely that there are more ways to reach the unsafe deserialization function (aswazuhobject), some of them might even be accessible from different contexts (without credentials, or initiated by a compromised agent). I suggest fixing the root cause instead of attempting to sanitize inputs that reach it. Note that there are multiple other ways to execute arbitrary code in aswazuhobject, easier by using a callable, or potentially abusing callable gadgets in exception, wresults or Wazuh.

CISA’s summary

Wazuh contains a deserialization of untrusted data vulnerability that allows for remote code execution on Wazuh servers.

Weakness type: CWE-502.

Product: Wazuh Wazuh Server · Assigned by: GitHub_M · Published: 2025-02-10

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: low (any account)
• User interaction: none
• Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: added 2025-06-10; federal due date 2025-07-01. Known ransomware use: Unknown.
• CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
• CISA SSVC assessment: exploitation active, automatable no, technical impact total.
• FIRST EPSS (model of 2026-10-21): 93.84% probability of exploitation activity in the next 30 days; percentile 99.8.

Timeline

• 2025-02-10 — CVE record published by GitHub_M
• 2025-04-22 — GitHub-reviewed advisory GHSA-hcrc-79hj-m3qh published (critical)
• 2025-06-10 — Added to CISA’s Known Exploited Vulnerabilities catalog
• 2025-07-01 — CISA remediation deadline for US federal agencies
• 2026-02-26 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. Listed in CISA KEV notes (wazuh.com) wazuh.com
2. Listed in CISA KEV notes (github.com) github.com

Vulnerability records

1. GitHub Advisory GHSA-hcrc-79hj-m3qh github.com
2. CVE.org record CVE-2025-24016 cve.org
3. NVD entry CVE-2025-24016 nvd.nist.gov

Government

1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov

All exploited Wazuh vulnerabilities · Critical Go advisories · Today’s Security Digest