Read the docs
TI-2026-85944 Aliases CVE-2026-112339

Missing TLS hostname verification in Wazuh fluent-forward module

Priority LOW 35CWE-297Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Wazuh from 3.9.0 before 4.14.9 does not verify the TLS hostname in the fluent-forward module's wm_fluent_ssl_ctx() function. A network attacker can impersonate the Fluentd collector by presenting any certificate that chains to the configured ca_file. An attacker who redirects the connection through DNS, ARP, or an on-path position can receive forwarded security telemetry and the shared_key_hexdigest, which can then be cracked offline (CWE-297).

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

Wazuh from 3.9.0 before 4.14.9 contains a missing TLS hostname verification vulnerability in the fluent-forward module's wm_fluent_ssl_ctx() that allows network attackers to impersonate the Fluentd collector by presenting any certificate chaining to the configured ca_file. Attackers who redirect the connection via DNS, ARP, or on-path positions can receive forwarded security telemetry and the shared_key_hexdigest for offline cracking.

Why it matters now

EPSS 0.00169 6th percentileScored 2026-11-07
Fix Fixed wazuh (wazuh): 4.14.9

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Wazuhwazuh3.9.0 to before 4.14.94.14.9Patch availableCNA
  • wazuh VendorWazuh Affected 3.9.0 to before 4.14.9 Fixed in 4.14.9 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*——Wazuh
  • cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:* Versions — — ·Wazuh

Remediation

Upgrade Wazuh to version 4.14.9.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

  • Fix · CNA wazuh (wazuh) Fixed in 4.14.9

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    wazuh 4.14.9

    7 records Highest priority Priority HIGH 1 HIGH, 6 LOW

    Other records, highest priority first

    • TI-2026-85943 Server-side request forgery in Wazuh GitHub module leaks API tokenPriority HIGH 69
    • TI-2026-85941 Wazuh Manager JSON Decoder Memory Leak Enables Denial of ServicePriority LOW 32
    • TI-2026-85946 SQL injection in Wazuh WazuhDBBackend exposes agent internal keysPriority LOW 31
    Show all 7 records →

Timeline

  1. 2026-11-06 Threatist record created from CVE-2026-112339
  2. 2026-11-08 Priority changed: MEDIUM → LOW

References

Advisory 1

Other 1

  • TI-2025-17783 Remote code execution in Wazuh server KEVCVSS 3.1CRITICAL 9.9
  • TI-2026-47604 Wazuh GitHub Actions Shell Injection via Fork Pull Request CVSS 4.0CRITICAL 9.3
  • TI-2026-71739 Missing origin check in Wazuh manager allows arbitrary file read CVSS 4.0HIGH 8.7
  • TI-2026-71743 Arbitrary file overwrite in Wazuh manager enables root code execution CVSS 4.0CRITICAL 9.4
  • TI-2026-23722 Path traversal in wazuh CVSS 3.1CRITICAL 9.9
  • TI-2024-01157 Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft CVSS 4.0CRITICAL 9.5
See all 101 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences