Quick answers
- Is CVE-2026-62365 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62365 being exploited in the wild.
- How severe is CVE-2026-62365?
- Medium severity, with a CVSS score of 5.3, published 4 November 2026.
- Which products and versions are affected?
- Wazuh prior to 4.14.7.
- Is there a fix for CVE-2026-62365?
- Yes: fixed in 4.14.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62365 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-62365?
- Check whether you run Wazuh at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.14.7
Technical details
A heap buffer overflow exists in DecodeWinevt's join_data accumulation logic in src/analysisd/decoders/winevtchannel.c: the snprintf size parameter uses the accumulated content length instead of the fixed 65,535-byte (OS_MAXSTR) buffer capacity, allowing out-of-bounds writes. An authenticated agent submitting four maximum-sized unnamed Data elements triggers a heap corruption that crashes wazuh-analysisd during the subsequent free() call, causing denial of service to all agents managed by that manager instance.
Affected products
- Wazuh Wazuh prior to 4.14.7
Timeline
- 2026-11-04: disclosed