Skip to content
Noroxi
CVE-2025-24016· NVD / CVE Program· CNA GitHub_M

Remote code execution in Wazuh server

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.

CriticalCVSS 9.9 · v3.1KEVWeaponized Fix available
Published
Feb 10, 2025
Updated
Jun 17, 2026
EPSS
93.8% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

97

Now

Patch today or shut off access.

CVSS
39 / 40 · 9.9 / 10
CISA KEV
30 / 30 · Listed
EPSS
28 / 30 · 93.8%

CISA SSVC decision

Exploitation
active
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
9.9
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Jun 10, 2025. That signals real attacks, not theory.

Remediation deadline for government agencies: Jul 1, 2025.

Affected systems

VendorProduct
wazuhwazuh

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • wazuh wazuh4.4.0 and later · before 4.9.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • wazuh wazuh

    • >= 4.4.0, < 4.9.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/wazuh/wazuhfrom 4.4.0 · before 4.9.14.9.1
Gogithub.com/wazuh/wazuhfrom 4.4.0+incompatible · before 4.9.1+incompatible4.9.1+incompatible
openSUSE:Tumbleweedgovulncheck-vulndbbefore 0.0.20250312T181707-1.10.0.20250312T181707-1.1

Other highest-scoring records for the same primary product.

  • CVE-2023-50260Wazuh's vulnerability in host_deny AR script allows arbitrary command execution
    47Plan
  • CVE-2021-44079In the wazuh-slack active response script in Wazuh 4.2.x before 4.2.5, untrusted user agents are passed to a curl command line, potentially
    40Plan
  • CVE-2026-30893Wazuh cluster sync path traversal in decompress_files() enables arbitrary file write and code execution from authenticated cluster peer
    39Monitor
  • CVE-2024-32038Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability
    39Monitor
  • CVE-2024-1243Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft
    38Monitor
  • CVE-2021-26814Wazuh API in Wazuh from 4.0.0 to 4.0.3 allows authenticated users to execute arbitrary code with administrative privileges via /manager/file
    38Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/wazuh/wazuh4.9.1Package registry (OSV)
Go:github.com/wazuh/wazuh4.9.1+incompatiblePackage registry (OSV)
opensuse:govulncheck-vulndb0.0.20250312T181707-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×8

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Metasploit moduleexploit/linux/http/wazuh_auth_rce_cve_2025_24016Wazuh server remote code execution caused by an unsafe deserialization vulnerability.exploit2025-02-10
Nuclei detection templateNuclei template CVE-2025-24016 —
Proof-of-concept repository on GitHubstars:42025-02-13
Proof-of-concept repository on GitHubstars:432025-02-16
Proof-of-concept repository on GitHubstars:62025-02-20
Proof-of-concept repository on GitHubstars:12025-02-21
Proof-of-concept repository on GitHubstars:02025-04-15
Proof-of-concept repository on GitHubstars:22025-04-21
Proof-of-concept repository on GitHubstars:22025-06-10
Proof-of-concept repository on GitHubstars:82025-07-13

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Metasploit-1 d
  2. Published
  3. First PoC+2 d
  4. CISA KEV+119 d
  5. TodaySep 30, 2026+597 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-25769400 days apartWazuh Cluster vulnerable to Remote Code Execution via Insecure Deserialization
    36Monitor
  • CVE-2026-28220525 days apartWazuh cluster DAPI arbitrary callable deserialization and RBAC context injection allow a cluster peer to execute privileged functions on the master node
    36Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
Low
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-secondary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python
payload = sock.recv(65536)job = pickle.loads(payload)

Fixed

python
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig):    raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records