Quick answers
- Is CVE-2026-112339 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112339 being exploited in the wild.
- How severe is CVE-2026-112339?
- Medium severity, with a CVSS score of 5.9, published 6 November 2026.
- Which products and versions are affected?
- Wazuh Agent 3.9.0 to 4.14.8; Wazuh Manager 3.9.0 to 4.14.8.
- Is there a fix for CVE-2026-112339?
- Yes: fixed in 4.14.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112339 attacked?
- It is attacked over the network or from the adjacent network, in a software library.
- Am I affected by CVE-2026-112339?
- Check whether you run Wazuh Agent or Wazuh Manager 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.9
Technical details
The wm_fluent_ssl_ctx() function in the fluent-forward module validates the TLS certificate chain but fails to verify that the peer certificate's subject or subjectAltName matches the configured Fluentd server address. An attacker on the network path (via DNS hijacking, ARP spoofing, or routing manipulation) who holds any certificate signed by the configured CA can intercept the connection and receive forwarded telemetry and the shared key authentication digest for offline cracking. The fix adds hostname verification using SSL_set1_host() after chain validation.
Affected products
- Wazuh Wazuh Agent 3.9.0 to 4.14.8
- Wazuh Wazuh Manager 3.9.0 to 4.14.8
Timeline
- 2026-11-06: disclosed
- 2026-10-15: patched: Wazuh v4.14.9 released with hostname verification added