Sensitive memory read via unterminated message buffer
Published Oct 29, 2025 · Updated Oct 29, 2025
Heap buffer over-read in Wazuh before 4.12.0 allows remote attackers controlling an agent to read beyond the manager's allocated memory. OS_CleanMSG() advances lf->log to the final allocated byte without placing a null terminator there, so w_expression_match() calls strlen() across the heap boundary. The read continues through adjacent heap bytes until a null byte; exploitation requires open agent enrollment or control of an existing agent.
Summary
What happened
Heap buffer over-read in Wazuh before 4.12.0 allows remote attackers controlling an agent to read beyond the manager's allocated memory. OS_CleanMSG() advances lf->log to the final allocated byte without placing a null terminator there, so w_expression_match() calls strlen() across the heap boundary. The read continues through adjacent heap bytes until a null byte; exploitation requires open agent enrollment or control of an existing agent.
The record
- CVE
- CVE-2025-62792
- Published
- Oct 29, 2025
- Updated
- Oct 29, 2025
- Vendor
- Wazuh
- Product
- Wazuh
- Classifications
- CWE-170, CWE-126, T1210
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 29, 2025CVE publishedPublication date reported by the CVE source.
- Oct 29, 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=< 4.12.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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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