CVE-2025-24016Known exploitationPublic exploitNetwork attack vector

Authenticated code execution via unsafe DAPI deserialization

Published Feb 10, 2025 · Updated Feb 26, 2026

Unsafe deserialization in Wazuh Server 4.4.0 through 4.9.0 allows remote authenticated users to execute arbitrary Python code. The as_wazuh_object hook in framework/wazuh/core/cluster/common.py accepts unsanitized DAPI dictionaries and interprets forged unhandled_exc content as Python objects. Reachability requires administrative API access, a compromised cluster peer, or, in certain configurations, a compromised agent; code executes on the server.

CVSS severity9.0
Critical
EPSS probability93.84%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Unsafe deserialization in Wazuh Server 4.4.0 through 4.9.0 allows remote authenticated users to execute arbitrary Python code. The as_wazuh_object hook in framework/wazuh/core/cluster/common.py accepts unsanitized DAPI dictionaries and interprets forged unhandled_exc content as Python objects. Reachability requires administrative API access, a compromised cluster peer, or, in certain configurations, a compromised agent; code executes on the server.

The record

CVE
CVE-2025-24016
Published
Feb 10, 2025
Updated
Feb 26, 2026
Vendor
Wazuh
Product
Wazuh
Classifications
CWE-502, CAPEC-586, T1059.006, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 10, 2025CVE publishedPublication date reported by the CVE source.
  2. Feb 26, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 4.4.0, < 4.9.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Wazuh · Wazuhversion=>= 4.4.0, < 4.9.1

Published CVSS scores

9.0GitHub Security AdvisoryCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H
9.9NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationReported
Public exploitPublished

Weakness, pattern, technique

CWE-502Deserialization of Untrusted Data
CAPEC-586Object Injection
T1059.006Python
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo