Manager code execution via permissions buffer underwrite
Published Oct 29, 2025 · Updated Oct 29, 2025
Heap buffer underwrite in Wazuh before 4.10.2 allows remote attackers controlling an enrolled agent to execute code on the manager. The decode_win_permissions function processes an oversized Windows permissions message, leaves decoded_it at the buffer start, and writes a NULL byte two bytes before that allocation. Reachability requires open agent enrollment or a compromised enrolled agent, and code execution depends on the manager's heap allocator; a crash is directly demonstrated.
Summary
What happened
Heap buffer underwrite in Wazuh before 4.10.2 allows remote attackers controlling an enrolled agent to execute code on the manager. The decode_win_permissions function processes an oversized Windows permissions message, leaves decoded_it at the buffer start, and writes a NULL byte two bytes before that allocation. Reachability requires open agent enrollment or a compromised enrolled agent, and code execution depends on the manager's heap allocator; a crash is directly demonstrated.
The record
- CVE
- CVE-2025-62786
- Published
- Oct 29, 2025
- Updated
- Oct 29, 2025
- Vendor
- Wazuh
- Product
- Wazuh
- Classifications
- CWE-124, 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.10.2
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
- Vendor advisory ASan 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