CVE-2026-41499: Wazuh: Multiple Heap-based NULL WRITE Buffer Underflows in parse_uname_string()
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 parseunamestring() (remotedop.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 SIZEMAX due to unsigned integer underflow. Due to pointer arithmetic wrapping, SIZEMAX 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41499?
CVE-2026-41499 is classified as a high severity vulnerability due to its potential for allowing remote code execution.
How do I fix CVE-2026-41499?
To fix CVE-2026-41499, upgrade Wazuh to version 4.14.4 or later.
What are the affected versions for CVE-2026-41499?
CVE-2026-41499 affects Wazuh versions from 4.0.0 to before 4.14.4.
What type of vulnerability is CVE-2026-41499?
CVE-2026-41499 is a heap-based NULL write buffer underflow vulnerability.
What impact does CVE-2026-41499 have on systems?
CVE-2026-41499 can lead to arbitrary code execution and potentially compromise the affected system's integrity.