https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 14:15:36 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-06586 bdu:2026-06586 https://cve.radiocsirt.org/vuln/bdu:2026-06586 https://cve.radiocsirt.org/vuln/euvd-2026-307958 EUVD-2026-307958 https://cve.radiocsirt.org/vuln/euvd-2026-307958 https://cve.radiocsirt.org/vuln/fkie_cve-2026-28221 <p>Wazuh is a free and open source platform used for threat prevention, detection, and response. From version 4.8.0 to before version 4.14.4, a stack-based buffer overflow exists in print_hex_string() in wazuh-remoted. The bug is triggered when formatting attacker-controlled bytes using sprintf(dst_buf + 2*i, &#34;%.2x&#34;, src_buf[i]) on platforms where char is treated as signed and the compiled code sign-extends bytes before the variadic call. For input bytes such as 0xFF, the formatting can emit &#34;ffffffff&#34; (8 chars) instead of &#34;ff&#34; (2 chars), causing an out-of-bounds write past a fixed 2049-byte stack buffer. The vulnerable path is reachable remotely prior to any agent authentication/registration logic via TCP/1514 when an oversized length prefix causes the “unexpected message (hex)” diagnostic path to run. Additionally, the same unauthenticated oversized-message diagnostic path logs an attacker-controlled hex dump to /var/ossec/logs/ossec.log for each trigger, allowing remote log amplification that can degrade monitoring fidelity and consume disk/I/O. This log amplification is reachable even without triggering the sign-extension overflow (e.g., using bytes &lt; 0x80). This issue has been patched in version 4.14.4.</p> <p>Wazuh is a free and open source platform used for threat prevention, detection, and response. From version 4.8.0 to before version 4.14.4, a stack-based buffer overflow exists in print_hex_string() in wazuh-remoted. The bug is triggered when formatting attacker-controlled bytes using sprintf(dst_buf + 2*i, &#34;%.2x&#34;, src_buf[i]) on platforms where char is treated as signed and the compiled code sign-extends bytes before the variadic call. For input bytes such as 0xFF, the formatting can emit &#34;ffffffff&#34; (8 chars) instead of &#34;ff&#34; (2 chars), causing an out-of-bounds write past a fixed 2049-byte stack buffer. The vulnerable path is reachable remotely prior to any agent authentication/registration logic via TCP/1514 when an oversized length prefix causes the “unexpected message (hex)” diagnostic path to run. Additionally, the same unauthenticated oversized-message diagnostic path logs an attacker-controlled hex dump to /var/ossec/logs/ossec.log for each trigger, allowing remote log amplification that can degrade monitoring fidelity and consume disk/I/O. This log amplification is reachable even without triggering the sign-extension overflow (e.g., using bytes &lt; 0x80). This issue has been patched in version 4.14.4.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-28221 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1295 <p>Ein Angreifer kann mehrere Schwachstellen in Wazuh ausnutzen, um einen Denial of Service Angriff durchzuführen, beliebigen Code auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder Sicherheitsmaßnahmen zu umgehen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Wazuh ausnutzen, um einen Denial of Service Angriff durchzuführen, beliebigen Code auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder Sicherheitsmaßnahmen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1295