Read the docs
TI-2026-85258 Aliases CVE-2026-62365

Heap buffer overflow in Wazuh EventChannel decoder crashes analysisd

Priority LOW 24CWE-122Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-122 and the CVSS impact.

Summary

Wazuh from 3.9.0 before 4.14.7 contains a heap-based buffer overflow in DecodeWinevt() in the EventChannel decoder (CWE-122). The function accumulates unnamed Data element contents into a fixed 65,535-byte heap buffer but uses the growing content length instead of the buffer capacity as the snprintf size. An enrolled agent that sends an EventChannel message with four maximum-sized unnamed Data elements can write past the buffer and corrupt heap metadata, which makes wazuh-analysisd terminate and stops log ingestion for all agents on that manager.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

Description from the CNA

Wazuh is an open-source security platform providing unified XDR and SIEM protection for endpoints and cloud workloads. DecodeWinevt in src/analysisd/decoders/winevtchannel.c accumulates unnamed Windows EventChannel Data element contents into the fixed 65,535-byte join_data heap buffer but passes the growing content length, rather than the OS_MAXSTR buffer capacity, as the snprintf size. An enrolled agent can submit an EventChannel message containing four maximum-sized unnamed Data elements, causing the fourth accumulation to write beyond join_data and corrupt adjacent heap metadata. The subsequent free of join_data2 causes the wazuh-analysisd process to terminate, stopping log ingestion for all agents handled by that manager. This vulnerability is fixed in 4.14.7.

Why it matters now

EPSS 0.00284 21st percentileScored 2026-11-07
Fix Fixed wazuh (wazuh): 4.14.7

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Wazuhwazuh3.9.0 to before 4.14.74.14.7Patch availableCNA
  • wazuh VendorWazuh Affected 3.9.0 to before 4.14.7 Fixed in 4.14.7 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*——Wazuh
  • cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:* Versions — — ·Wazuh

Remediation

Upgrade Wazuh to version 4.14.7, which contains the fix. The sources list no fixed version for other Wazuh branches.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

  • Fix · CNA wazuh (wazuh) Fixed in 4.14.7

Timeline

  1. 2026-11-04 Threatist record created from CVE-2026-62365

References

Other 4

  • TI-2025-17783 Remote code execution in Wazuh server KEVCVSS 3.1CRITICAL 9.9
  • TI-2026-47604 Wazuh GitHub Actions Shell Injection via Fork Pull Request CVSS 4.0CRITICAL 9.3
  • TI-2026-71739 Missing origin check in Wazuh manager allows arbitrary file read CVSS 4.0HIGH 8.7
  • TI-2026-71743 Arbitrary file overwrite in Wazuh manager enables root code execution CVSS 4.0CRITICAL 9.4
  • TI-2026-23722 Path traversal in wazuh CVSS 3.1CRITICAL 9.9
  • TI-2024-01157 Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft CVSS 4.0CRITICAL 9.5
See all 101 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences