Wazuh
Wazuh has Privilege Escalation to Root via Cluster Protocol File Write
Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 3.9.0 and prior to version 4.14.3, a privilege escalation vulnerability exists in the Wazuh Manager's cluster synchronization protocol. The `wazuh-clusterd` service allows authenticated nodes to write arbitrary files to the manager’s file system with the permissions of the `wazuh` system user. Due to insecure default permissions, the `wazuh` user has write access to the manager's main configuration file (`/var/ossec/etc/ossec.conf`). By leveraging the cluster protocol to overwrite `ossec.conf`, an attacker can inject a malicious `<localfile>` command block. The `wazuh-logcollector` service, which runs as root, parses this configuration and executes the injected command. This chain allows an attacker with cluster credentials to gain full Root Remote Code Execution, violating the principle of least privilege and bypassing the intended security model. Version 4.14.3 fixes the issue.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.9.0, < 4.14.3
Fixed in 4.14.3
Mitigation
Upgrade wazuh to 4.14.3 or later.
References
- Vendor advisory github.com/wazuh/wazuh/security/advisories/GHS…
Timeline
Days relative to CVE publicationFirst public PoC 3.8 days after publication; not in CISA KEV. First PoC: Samres27/CVE-2026-25769---CVE-2026-25770 (created 21 Mar 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Samres27/CVE-2026-25769---CVE-2026-25770 | 21 Mar 2026 +3.8 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.