CVE-2026-25770: 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 Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25770?
CVE-2026-25770 is classified as a high severity vulnerability due to its potential for privilege escalation to root.
How do I fix CVE-2026-25770?
To fix CVE-2026-25770, upgrade Wazuh Manager to version 4.14.3 or later.
What impacts does CVE-2026-25770 have on Wazuh Manager users?
CVE-2026-25770 allows unauthorized users to escalate their privileges and potentially gain root access.
Which versions of Wazuh are affected by CVE-2026-25770?
Wazuh versions between 3.9.0 and 4.14.3 are affected by CVE-2026-25770.
Is there a workaround for CVE-2026-25770?
There are currently no known workarounds for CVE-2026-25770, so updating to a fixed version is recommended.