Wazuh is a free and open source platform used for threat prevention, detection, and response. Prior to 4.11.0, w_copy_event_for_log() references memory (initially allocated in OS_CleanMSG()) after it has been freed. A compromised agent can potentially compromise the integrity of the application by sending a specially crafted message to the wazuh manager. An attacker who is able to craft and send an agent message to the wazuh manager can leverage this issue to potentially compromise the integrity of the application (the use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere). This vulnerability is fixed in 4.11.0.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/wazuh/wazuh/security/advisories/GHSA-qjcw-fjvh-8q4g Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.3 · wazuhNVD modified 2026-10-19 13:10
Affected (CPE criteria) 1
cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*
References 1
- https://github.com/wazuh/wazuh/security/advisories/GHSA-qjcw-fjvh-8q4g Exploit, Vendor Advisory