CVE-2026-46343: Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6…
CVE-2026-46343 · Severity: high · CVSS 7.2 · Published 2026-08-19
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta2, WazuhCommon.end_receiving_file() in framework/wazuh/core/cluster/common.py allows a cluster-authenticated node to delete files outside WAZUH_PATH. A syn_i_w_m_e request with an unknown task_id reaches the cleanup branch, where an attacker-controlled filename is passed to os.path.join without canonicalization or confinement. Absolute paths and traversal sequences can therefore target files such as ossec.conf, jwt_secret.json, TLS certificates, and ruleset files that are accessible to the Wazuh manager process. Deletion can disable the manager, invalidate API tokens, or disrupt cluster and API connectivity. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.
No. Junglewise Threat Intelligence has no report of CVE-2026-46343 being exploited in the wild.
How severe is CVE-2026-46343?
High severity, with a CVSS score of 7.2, published 19 August 2026.
Which products and versions are affected?
Wazuh. The advisory does not name versions.
Is there a fix for CVE-2026-46343?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-46343?
Check whether you run Wazuh. 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.