Service crash via empty-filename buffer underwrite
Published Apr 29, 2026 · Updated Apr 29, 2026
Heap buffer underwrite in Wazuh 1.0.0 through 4.14.3 allows local users with alert-log access to crash wazuh-logcollector. GetAlertData subtracts one from the unsigned length of an empty duplicated filename, wraps the index, and writes a null byte immediately before the heap buffer. Exploitation requires an ossecalert-formatted monitored log and a crafted syscheck alert containing an empty filename; the demonstrated consequence is service interruption through heap corruption.
Summary
What happened
Heap buffer underwrite in Wazuh 1.0.0 through 4.14.3 allows local users with alert-log access to crash wazuh-logcollector. GetAlertData subtracts one from the unsigned length of an empty duplicated filename, wraps the index, and writes a null byte immediately before the heap buffer. Exploitation requires an ossecalert-formatted monitored log and a crafted syscheck alert containing an empty filename; the demonstrated consequence is service interruption through heap corruption.
The record
- CVE
- CVE-2026-26204
- Published
- Apr 29, 2026
- Updated
- Apr 29, 2026
- Vendor
- Wazuh
- Product
- Wazuh
- Classifications
- CWE-124, CWE-191
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 29, 2026CVE publishedPublication date reported by the CVE source.
- Apr 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.0.0, < 4.14.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA crafted-alert proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo