Skip to main content

Wazuh Manager CVE-2025-62791

MEDIUM
Unchecked Return Value (CWE-252)
2025-10-29 security-advisories@github.com
6.9
CVSS 4.0 · Vendor: github
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Compromise or enroll a Wazuh agent
  2. Delivery
    Craft malformed CISCAT message
  3. Exploit
    Send to manager over agent channel
  4. Execution
    Trigger NULL deref in DecodeCiscat()
  5. Impact
    Crash analysisd, disable detection

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Return value checking
Exploitation Conditions

Exploitation requires the ability to deliver an agent message to the Wazuh manager's analysisd via the agent communication channel - the description frames this as 'a compromised agent,' implying the attacker must control or impersonate an endpoint that is already enrolled with a valid agent key. The specific trigger is a malformed CISCAT-formatted message that causes cJSON_GetObjectItem() to return NULL in DecodeCiscat(). Limiting factors: the attacker needs prior agent compromise or valid enrollment (not arbitrary internet-facing unauthenticated access), the impact is confined to crashing analysisd (availability only, no data exposure or code execution), and only Wazuh manager versions prior to 4.11.0 are affected.

Impact

This is a legitimately moderate issue rather than an inflated high-CVSS finding. The CVSS 4.0 vector (6.9, AV:N/AC:L/PR:N/UI:N) scores availability-only impact (VA:L) with no confidentiality or integrity effect, which is consistent with CWE-252 (unchecked return value) causing a NULL-pointer dereference crash in analysisd rather than code execution. However, the vendor-supplied PR:N conflicts with the description: exploitation requires 'a compromised agent' or an attacker 'able to craft and send an agent message to the wazuh manager,' which in practice presupposes a validly enrolled/authenticated agent (agent key). I assess this as effectively authenticated (PR:L) - verify against the Wazuh advisory. No EPSS score, KEV listing, or public POC was provided, so exploitation probability signals are absent; per available data this is 'no public exploit identified at time of analysis.' Net: a real but bounded denial-of-service risk against the manager's analysis engine, most relevant where an adversary can already compromise an endpoint agent.

Exploit ScenarioDerived

An attacker who has compromised a host running an enrolled Wazuh agent (or otherwise obtained a valid agent key) sends a specially crafted CISCAT-type message to the Wazuh manager. DecodeCiscat() fails to check the NULL return of cJSON_GetObjectItem() on malformed input and dereferences it, crashing the analysisd process and halting threat detection/alerting. No public exploit code was identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 19, 2026

Wazuh Manager versions before 4.11.0 present a legitimately moderate denial-of-service issue rather than an inflated high-CVSS finding: analysisd can be crashed by a malformed CISCAT message sent through the agent communication channel. The attacker must control or impersonate an already enrolled agent, or have compromised an endpoint with a valid agent key, so this is not arbitrary unauthenticated internet access. Impact is limited to availability of analysisd, with no data exposure or code execution; no public exploit or CISA KEV entry was identified at time of analysis, and the vendor-released fix is 4.11.0.

RemediationAI

Vendor-released patch: 4.11.0. Upgrade the Wazuh Manager to 4.11.0 or later, and verify the analysisd service is running the updated build after deployment; the advisory is https://github.com/wazuh/wazuh/security/advisories/GHSA-gcwf-6p6m-gvm7. If immediate upgrade is not possible, reduce exposure by ensuring only trusted endpoints can enroll and by promptly revoking or rotating agent keys for any compromised hosts, since the trigger requires a valid agent communication channel; segment manager agent-facing ports so untrusted networks cannot deliver agent messages, and monitor analysisd for crashes or unexpected restarts while reviewing agent messages for malformed CISCAT payloads. These compensating controls do not eliminate the parser bug and carry operational trade-offs: tighter enrollment and port restrictions can block legitimate agents, and key rotation can disrupt reporting until agents are re-enrolled.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Wazuh is an open-source security platform whose manager runs analysisd to decode and analyze events received from enrolled agents. The CISCAT decoder processes CIS-CAT compliance scan results in JSON and uses cJSON_GetObjectItem() to retrieve fields; CWE-252 (Unchecked Return Value) means DecodeCiscat() does not check whether that function returned NULL before dereferencing it. A crafted CISCAT message can therefore trigger a null-pointer dereference and crash analysisd. The CPE wildcard cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:* scopes all pre-4.11.0 Wazuh builds under the advisory, but the vulnerable target is the manager's analysisd and delivery requires the agent communication channel with a valid enrolled or compromised agent identity. The published CVSS 4.0 vector (6.9, PR:N) differs from the independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L), which better reflects the agent-level prerequisite and availability-only impact.

Know when Wazuh gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (github) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Requires a valid/compromised enrolled agent to send the message, so PR:L not PR:N; network-delivered and low-complexity, availability-only crash so C:N/I:N/A:L.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (github).

CVSS VectorVendor: github

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Wazuh is a free and open source platform used for threat prevention, detection, and response. Prior to 4.11.0, DecodeCiscat() implementation does not check the return the value of cJSON_GetObjectItem() for a possible NULL value in case of an error. A compromised agent can cause a crash of analysisd by sending a specially crafted message to the wazuh manager. An attacker who is able to craft and send an agent message to the wazuh manager can cause analysisd to crash and make it unavailable. This vulnerability is fixed in 4.11.0.

Threat Intelligence Overview

EPSS Score
0.3%
Top 75% exploitable
Prevalence
Medium
popular open-source SIEM/XDR, common in security teams but not universal
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

Affected Products (CPE)CVE.org

cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*

More in Wazuh

View all
CVE-2025-24016 CRITICAL POC
9.9 Feb 10

Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t

CVE-2021-44079 CRITICAL POC
9.8 Nov 22

In the wazuh-slack active response script in Wazuh 4.2.x before 4.2.5, untrusted user agents are passed to a curl comman

CVE-2026-48024 CRITICAL POC
9.1 Aug 19

Path-traversal-driven root code execution affects the Wazuh security platform's cluster synchronization layer in version

CVE-2026-48162 CRITICAL POC
9.1 Aug 19

Arbitrary file read in Wazuh cluster deployments (4.0.0 through 4.14.5, and 5.0.0-beta1/beta2) lets a peer node that alr

CVE-2026-61800 CRITICAL POC
9.1 Aug 27

Arbitrary file write leading to root remote code execution affects Wazuh worker nodes in clustered deployments running v

CVE-2026-25769 CRITICAL POC
9.1 Mar 17

A critical deserialization vulnerability in Wazuh's cluster mode allows attackers with access to any worker node to achi

CVE-2025-30201 CRITICAL POC
9.1 Nov 21

Wazuh Agent before 4.13.0 on Windows can be made by an authenticated, high-privileged configuration writer to open attac

CVE-2026-44901 HIGH POC
8.4 Aug 19

Remote code execution on the Wazuh cluster master node is achievable by any attacker who controls a cluster worker node,

CVE-2026-54083 HIGH POC
8.1 Aug 27

Path traversal in Wazuh's ip-customblock active response script allows low-privileged remote attackers to create or dele

CVE-2018-19666 HIGH POC
7.8 Nov 29

The agent in OSSEC through 3.1.0 on Windows allows local users to gain NT AUTHORITY\SYSTEM access via Directory Traversa

CVE-2026-44252 HIGH POC
7.7 Aug 19

Cluster key disclosure in Wazuh Manager versions 4.0.0 through 4.14.4 enables a two-stage privilege escalation: a low-pr

CVE-2026-71540 HIGH POC
7.5 Sep 24

Unauthenticated remote denial of service in the Wazuh cluster daemon (wazuh-clusterd) allows a network peer to exhaust p

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy