Arbitrary file deletion via path traversal
Published Aug 19, 2026 · Updated Aug 19, 2026
Path traversal in Wazuh before 4.14.6 and 5.0.0-beta2 allows remote authenticated users to delete manager files via cluster sync messages. In WazuhCommon.end_receiving_file() in framework/wazuh/core/cluster/common.py, an unknown syn_i_w_m_e task_id reaches a cleanup path that joins an attacker-controlled filename without canonicalization or confinement, so absolute paths and traversal sequences escape WAZUH_PATH. Reachability requires a cluster-authenticated node in a clustered deployment, and deletion is limited to files the manager process can remove, including configuration, token, certificate, and ruleset files that can disable the manager or break API and cluster connectivity.
Summary
What happened
Path traversal in Wazuh before 4.14.6 and 5.0.0-beta2 allows remote authenticated users to delete manager files via cluster sync messages. In WazuhCommon.end_receiving_file() in framework/wazuh/core/cluster/common.py, an unknown syn_i_w_m_e task_id reaches a cleanup path that joins an attacker-controlled filename without canonicalization or confinement, so absolute paths and traversal sequences escape WAZUH_PATH. Reachability requires a cluster-authenticated node in a clustered deployment, and deletion is limited to files the manager process can remove, including configuration, token, certificate, and ruleset files that can disable the manager or break API and cluster connectivity.
The record
- CVE
- CVE-2026-46343
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- Wazuh
- Product
- Wazuh
- Classifications
- CWE-22, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.0.0, < 4.14.6
- Affected versionversion=>= 5.0.0-beta1, < 5.0.0-beta2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo