Read the docs
TI-2026-34063 Aliases CVE-2026-46343

Wazuh: Arbitrary File Deletion via Cluster Protocol – Incomplete Path Validation in end_receiving_file()

Priority HIGH 68CWE-22Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00423 36th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed wazuh (wazuh): 4.14.6, 5.0.0-beta2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Wazuhwazuh4.0.0 to before 4.14.6; 5.0.0-beta1 to before 5.0.0-beta24.14.6, 5.0.0-beta2Patch availableCNA
  • wazuh VendorWazuh Affected 4.0.0 to before 4.14.6; 5.0.0-beta1 to before 5.0.0-beta2 Fixed in 4.14.6, 5.0.0-beta2 Patch available CNA

CPE configurations NVD · 2

CPEVersionsRoleVendor
cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*4.0.0 to before 4.14.6VulnerableWazuh
cpe:2.3:a:wazuh:wazuh:5.0.0:beta1:*:*:*:*:*:*5.0.0 beta1VulnerableWazuh
  • cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:* Versions 4.0.0 to before 4.14.6 Vulnerable ·Wazuh
  • cpe:2.3:a:wazuh:wazuh:5.0.0:beta1:*:*:*:*:*:* Versions 5.0.0 beta1 Vulnerable ·Wazuh

Remediation

  • Fix · CNA wazuh (wazuh) Fixed in 4.14.6, 5.0.0-beta2

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-46343

References

Exploit 1

Patch 4

  • TI-2025-17783 Remote code execution in Wazuh server KEVCVSS 3.1CRITICAL 9.9
  • TI-2026-23722 Path traversal in wazuh CVSS 3.1CRITICAL 9.9
  • TI-2024-01157 Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft CVSS 4.0CRITICAL 9.5
  • TI-2026-22556 Wazuh: Pre-auth stack-based buffer overflow in wazuh-remoted print_hex_string() due to signed char promotion on x86_64 CVSS 3.1HIGH 8.2
  • TI-2026-35598 Wazuh: cluster peer can read arbitrary master files and forge offline REST API… CVSS 3.1CRITICAL 9.1
  • TI-2026-35467 Wazuh: merged-file header path traversal in cluster sync allows arbitrary file write under WAZUH_PATH in Wazuh manager CVSS 3.1CRITICAL 9.1
See all 72 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences