CVE-2026-46343
Wazuh is a free and open source platform used for threat …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/wazuh/wazuh/commit/90d43547d166cdbe65e9a3d011f946214df9179c
- github.com/wazuh/wazuh/pull/36060
- github.com/wazuh/wazuh/releases/tag/v4.14.6
- github.com/wazuh/wazuh/releases/tag/v5.0.0-beta2
- github.com/wazuh/wazuh/security/advisories/GHSA-cqvw-w2rg-327f
- nvd.nist.gov/vuln/detail/CVE-2026-46343
- cve.org/CVERecord?id=CVE-2026-46343
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.