Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-41499— Wazuh: Multiple Heap-based NULL WRITE Buffer Underflows in parse_uname_string()

Quick assessment

Affected
wazuh wazuh
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Wazuh是Wazuh开源的一个应用软件。用于收集,汇总,索引和分析安全数据,帮助组织检测入侵,威胁和行为异常。 Wazuh 4.0.0版本至4.14.4之前版本存在安全漏洞,该漏洞源于parse_uname_string函数中存在多个基于堆的越界写入漏洞,该函数处理来自代理的操作系统识别数据,在4个位置存在危险代码模式,当字符串为空时strlen返回0,0减1因无符号整数下溢导致SIZE_MAX,指针算术环绕使SIZE_MAX变为-1,导致在分配缓冲区前1字节处写入,破坏堆元数据,可能导致堆损坏。

CVSS 6.5 · Medium EPSS 0.45% · P36

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application

Affected Version Matrix 1

VendorProduct Version RangeStatus
wazuh wazuh >= 4.0.0, < 4.14.4 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-41499

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Wazuh: Multiple Heap-based NULL WRITE Buffer Underflows in parse_uname_string()
Source: CVE Program / CVE List V5
Vulnerability Description
Wazuh is a free and open source platform used for threat prevention, detection, and response. From version 4.0.0 to before version 4.14.4, multiple heap-based out-of-bounds WRITE vulnerabilities exist in parse_uname_string() (remoted_op.c). This function processes OS identification data from agents and contains a dangerous code pattern that appears in 4 locations within the same function: writing to strlen(ptr) - 1 without checking for empty strings. When the string is empty, strlen() returns 0, and 0 - 1 wraps to SIZE_MAX due to unsigned integer underflow. Due to pointer arithmetic wrapping, SIZE_MAX effectively becomes -1, causing a write exactly 1 byte before the allocated buffer. This corrupts heap metadata (e.g., the chunk size field in glibc malloc), leading to heap corruption. This issue has been patched in version 4.14.4.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
缓冲区下溢
Source: CVE Program / CVE List V5
Vulnerability Title
Wazuh 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Wazuh是Wazuh开源的一个应用软件。用于收集,汇总,索引和分析安全数据,帮助组织检测入侵,威胁和行为异常。 Wazuh 4.0.0版本至4.14.4之前版本存在安全漏洞,该漏洞源于parse_uname_string函数中存在多个基于堆的越界写入漏洞,该函数处理来自代理的操作系统识别数据,在4个位置存在危险代码模式,当字符串为空时strlen返回0,0减1因无符号整数下溢导致SIZE_MAX,指针算术环绕使SIZE_MAX变为-1,导致在分配缓冲区前1字节处写入,破坏堆元数据,可能导致堆损坏。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
wazuh wazuh >= 4.0.0, < 4.14.4 -

II. Public POCs for CVE-2026-41499

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-41499

请登录查看更多情报信息。

Vendor Advisories for CVE-2026-41499 (1)

Vendor Pages for CVE-2026-41499 (1)

Same Patch Batch · wazuh · 2026-04-29 · 5 CVEs total

CVE-2026-30893 9.0 CRITICAL Wazuh cluster sync path traversal in decompress_files() enables arbitrary file write and c
CVE-2026-26206 6.5 MEDIUM Wazuh: API brute-force protection bypass via race condition in login attempt tracking
CVE-2026-28221 6.5 MEDIUM Wazuh: Pre-auth stack-based buffer overflow in wazuh-remoted print_hex_string() due to sig
CVE-2026-26204 4.4 MEDIUM Wazuh: Heap-based NULL WRITE Buffer Underflow in GetAlertData

IV. Related Vulnerabilities

V. Comments for CVE-2026-41499

No comments yet


Leave a comment