Skip to content
Vulnerability Intelligence

CVE-2025-24016

CriticalExploitedPublic exploit

Wazuh server vulnerable to remote code execution

Published Apr 22, 2025 · Updated Aug 12, 2026 · Also known as GHSA-hcrc-79hj-m3qh, GO-2025-3459

Key Facts

Patch immediately
  • CVE-2025-24016 is a critical-severity vulnerability (CVSS 9.9 v3.1) affecting Wazuh, github.com/wazuh/wazuh (go), govulncheck-vulndb (suse) and 2 more products.
  • It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since May 3, 2025. Public exploit code is available.
  • EPSS estimates a 94% probability of exploitation in the next 30 days.
  • Fixed versions are available, including github.com/wazuh/wazuh 4.9.1, github.com/wazuh/wazuh 4.9.1+incompatible, govulncheck-vulndb 0.0.20250312T181707-1.1.
  • Brandefense priority: patch immediately, because it is listed as exploited in the wild.

CVSS v3.1

9.9

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

EPSS (30-day exploit likelihood)

94%

Higher than 99.8% of all scored CVEs

Exploited in the wild

Yes

4 catalog listings

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2025-24016 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

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.

Known-Exploited Catalog Listings

CatalogAddedRemediation dueRansomware use
CISA KEVJun 10, 2025Jul 1, 2025Not reported
Industry KEV feedMay 3, 2025Jul 1, 2025Not reported
CIRCL KEVMay 3, 2025Jul 1, 2025Not reported
ENISA EUVDJun 10, 2025n/aNot reported

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.

Affected Products

6 affected entries in total
ProductAffected versionsFixed in
WazuhWazuh>= >= 4.4.0, < 4.9.14.9.1
github.com/wazuh/wazuhgo>= 4.4.04.9.1
govulncheck-vulndbsuseSee advisory0.0.20250312T181707-1.1
wazuh/wazuhgithub-repoSee advisoryn/a
wazuh-manager>= 4.4.0>= 4.9.1

Patched Releases

github.com/wazuh/wazuh

4.9.1, 4.9.1+incompatible

govulncheck-vulndb

0.0.20250312T181707-1.1

Wazuh

4.9.1

wazuh-manager

>= 4.9.1

Timeline

  1. Publicly disclosed

    Apr 22, 2025

  2. Added to Industry KEV feed

    May 3, 2025

  3. Added to CIRCL KEV

    May 3, 2025

  4. Added to CISA KEV

    Jun 10, 2025

  5. Added to ENISA EUVD

    Jun 10, 2025

  6. Last updated

    Aug 12, 2026

Weakness Type

  • CWE-502 Deserialization of Untrusted Data

References

12 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2025-24016 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.

Request A Demo