CVE-2026-28221
Last modified
CVE-2026-28221 is a high-severity vulnerability rated 8.2/10 on the CVSS scale. 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. EPSS estimates a 0.38% chance of exploitation in the next 30 days.
Description
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, "%.2x", 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 "ffffffff" (8 chars) instead of "ff" (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 < 0x80). This issue has been patched in version 4.14.4.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wazuh | Wazuh | >= 4.8.0, < 4.14.4 |
References
- https://github.com/wazuh/wazuh/releases/tag/v4.14.4Release Notes
- https://github.com/wazuh/wazuh/security/advisories/GHSA-q9vv-7w4c-f4cmExploit, Vendor Advisory
- https://github.com/wazuh/wazuh/security/advisories/GHSA-q9vv-7w4c-f4cmExploit, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-28221?
How severe is CVE-2026-28221?
How do I fix CVE-2026-28221?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-28216hoppscotch is an open source API development ecosystem. Prio…8.3
- CVE-2026-28217hoppscotch is an open source API development ecosystem. Prio…6.5
- CVE-2026-28218Discourse is an open source discussion platform. Prior to ve…5.4
- CVE-2026-28219Discourse is an open source discussion platform. Prior to ve…4.3
- CVE-2026-2822A security vulnerability has been detected in JeecgBoot up t…8.8
- CVE-2026-28220Wazuh is a free and open source platform used for threat pre…9.1
- CVE-2026-28222Wagtail is an open source content management system built on…6.1
- CVE-2026-28223Wagtail is an open source content management system built on…6.1
- CVE-2026-28224Firebird is an open-source relational database management sy…8.2
- CVE-2026-28225Manyfold is an open source, self-hosted web application for …6.5
- CVE-2026-28226Phishing Club is a phishing simulation and man-in-the-middle…6.5
- CVE-2026-28227Discourse is an open source discussion platform. Prior to ve…2.7
Are you affected by CVE-2026-28221?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
