CVE-2026-25790: Wazuh has Stack-Based Buffer Overflow in Security Configuration Assessment JSON Parser
Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 3.9.0 and prior to version 4.14.3, multiple stack-based buffer overflows exist in the Security Configuration Assessment (SCA) decoder (wazuh-analysisd). The use of sprintf with a floating-point (%lf) format specifier on a fixed-size 128-byte buffer allows a remote attacker to overflow the stack. A specially crafted JSON event can trigger this overflow, leading to a denial of service (crash) or potential RCE on the Wazuh manager. The vulnerability is located in /src/analysisd/decoders/securityconfigurationassessment.c, within the FillScanInfo and FillCheckEventInfo functions. In multiple locations, a 128-byte buffer (char value[OSSIZE128];) is allocated on the stack to hold the string representation of a number from a JSON event. The code checks if the number is an integer or a double. If it's a double, it uses sprintf(value, "%lf", ...) to perform the conversion. This sprintf call is unbounded. If a floating-point number with a large exponent (e.g., 1.0e150) is provided, sprintf will attempt to write its full string representation (a "1" followed by 150 zeros), which is larger than the 128-byte buffer, corrupting the stack. Version 4.14.3 patches the issue.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25790?
CVE-2026-25790 is classified as a critical vulnerability due to its potential for stack-based buffer overflow exploitation.
How do I fix CVE-2026-25790?
To resolve CVE-2026-25790, upgrade Wazuh to version 4.14.3 or later.
What versions of Wazuh are affected by CVE-2026-25790?
CVE-2026-25790 affects Wazuh versions starting from 3.9.0 up to, but not including, 4.14.3.
What is the impact of CVE-2026-25790 on Wazuh?
The exploitation of CVE-2026-25790 can lead to remote code execution due to stack-based buffer overflow vulnerabilities.
Are there any workarounds for CVE-2026-25790 if I can't upgrade?
There are no documented workarounds for CVE-2026-25790; upgrading to a patched version is recommended.