Description
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-beta3, cluster.unmerge_info() in framework/wazuh/core/cluster/cluster.py constructs paths from peer-controlled merge_type and name values in a merged synchronization archive. process_files_from_worker() in framework/wazuh/core/cluster/master.py does not adequately confine the resulting path to the declared cluster item directory. A cluster peer holding the shared Fernet key can use traversal in files_metadata.json or a merged-file header to write files such as /var/ossec/etc/ossec.conf. Replacing ossec.conf can configure root-executed commands and lead to code execution when Wazuh services reload. This issue is fixed in versions 4.14.6 and 5.0.0-beta3.
Affected products
wazuh: wazuh
References6
- github.com/wazuh/wazuh/security/advisories/GHSA-gh4h-fx78-q8xc ExploitVendor Advisory
- github.com/wazuh/wazuh/security/advisories/GHSA-gh4h-fx78-q8xc ExploitVendor Advisory
- github.com/wazuh/wazuh/commit/88fc89fdfb1bf37b9d826e9c281a3d226… Patch
- github.com/wazuh/wazuh/pull/36204 Issue TrackingPatch
- github.com/wazuh/wazuh/releases/tag/v4.14.6 PatchRelease Notes
- github.com/wazuh/wazuh/releases/tag/v5.0.0-beta3 PatchRelease Notes
Metrics
- CVSS 3.1
-
9.1
CRITICAL
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 56 · as of 10 November 2026
- CWE
- CWE-22
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.