CVE-2026-26204: Wazuh: Heap-based NULL WRITE Buffer Underflow in GetAlertData
Wazuh is a free and open source platform used for threat prevention, detection, and response. From version 1.0.0 to before version 4.14.4, a heap-based out-of-bounds WRITE occurs in GetAlertData, resulting in writing a NULL byte exactly 1 byte before the start of the buffer allocated by strdup. Due to unsigned integer underflow and pointer arithmetic wrapping, the write lands at offset -1 from the buffer, corrupting heap metadata. A malicious actor can potentially leverage this issue through a compromised agent to cause denial of service or heap corruption by injecting a specially crafted alert into the alerts log file monitored by wazuh-logcollector. This issue has been patched in version 4.14.4.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-26204?
CVE-2026-26204 is rated as a high-severity vulnerability due to the potential for exploitation leading to heap-based buffer underflow.
How do I fix CVE-2026-26204?
The recommended fix for CVE-2026-26204 is to upgrade Wazuh to version 4.14.4 or later.
What versions of Wazuh are affected by CVE-2026-26204?
CVE-2026-26204 affects Wazuh versions from 1.0.0 up to, but not including, 4.14.4.
What type of issue is CVE-2026-26204 classified as?
CVE-2026-26204 is classified as a heap-based NULL write buffer underflow vulnerability.
Can CVE-2026-26204 be exploited remotely?
Yes, CVE-2026-26204 can potentially be exploited remotely, making it critical to apply the necessary updates.