Wazuh up to 4.14.5/5.0.0-beta1 Cluster Common common.py WazuhCommon.end_receiving_file path traversal

Summaryinfo

A vulnerability was found in Wazuh up to 4.14.5/5.0.0-beta1 and classified as very critical. Affected is the function WazuhCommon.end_receiving_file of the file framework/wazuh/core/cluster/common.py of the component Cluster Common. Such manipulation leads to path traversal. This vulnerability is traded as CVE-2026-46343. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as very critical, has been found in Wazuh up to 4.14.5/5.0.0-beta1. Affected by this issue is the function WazuhCommon.end_receiving_file of the file framework/wazuh/core/cluster/common.py of the component Cluster Common. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is handled as CVE-2026-46343 since 05/13/2026. The exploitation is known to be easy. The attack may be launched remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/19/2026). This vulnerability is assigned to T1006 by the MITRE ATT&CK project.

Upgrading to version 4.14.6 or 5.0.0-beta2 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• Wazuh

Version

• 4.14.0
• 4.14.1
• 4.14.2
• 4.14.3
• 4.14.4
• 4.14.5
• 5.0.0-beta1

Website

• Product: https://github.com/wazuh/wazuh/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion