Service crash via XML parser out-of-bounds read
Published Sep 27, 2025 · Updated Sep 27, 2025
Heap buffer overflow in wazuh-analysisd in Wazuh 3.8.0 through releases before 4.11.0 allows remote authenticated users to crash the service. While parsing crafted Windows EventChannel XML, _xml_sgetc reads one byte past the allocated buffer through _oscomment and _ReadElem. A low-privileged network sender able to submit EventChannel messages can terminate wazuh-analysisd, interrupting event analysis without reported data disclosure or modification.
Summary
What happened
Heap buffer overflow in wazuh-analysisd in Wazuh 3.8.0 through releases before 4.11.0 allows remote authenticated users to crash the service. While parsing crafted Windows EventChannel XML, _xml_sgetc reads one byte past the allocated buffer through _oscomment and _ReadElem. A low-privileged network sender able to submit EventChannel messages can terminate wazuh-analysisd, interrupting event analysis without reported data disclosure or modification.
The record
- CVE
- CVE-2025-59938
- Published
- Sep 27, 2025
- Updated
- Sep 27, 2025
- Vendor
- Wazuh
- Product
- Wazuh
- Classifications
- CWE-122, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 27, 2025CVE publishedPublication date reported by the CVE source.
- Sep 27, 2025Record 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=>= 3.8.0, < 4.11.0
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.
Public exploit references
- Vendor-published wazuh-analysisd crash 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