CVE-2026-74040 – Wazuh Manager
“One rogue agent or cluster worker is all it takes to turn Wazuh from the watcher into the weapon, with root on the manager and every host it protects.”
Wazuh Manager 4.14.8 closes six vulnerabilities in the central manager, two of them Critical, all reachable from enrolled agents, cluster workers, or user accounts the platform already trusts. CVE-2026-74040 has a CVSS score of 9.1, Critical severity; a cluster worker can overwrite protected master files such as ossec.conf and agent.conf, achieving root remote code execution across the manager and every agent. CVE-2026-74043 has a CVSS score of 9.0, Critical severity; a malicious worker holding the cluster key can use path traversal in rule, decoder, and list uploads to write files at arbitrary paths as the wazuh user.
The release also fixes four High-severity flaws. CVE-2026-74034 has a CVSS score of 7.5, High severity, and lets any enrolled agent read arbitrary files as root, including /etc/shadow and client.keys. CVE-2026-74035 has a CVSS score of 7.2, High severity, and lets a delegated user administrator submit an empty password to take over the wazuh superuser account. CVE-2026-74037 has a CVSS score of 7.2, High severity, and lets administrators whose access was revoked keep authenticating because issued tokens are never checked against the blacklist. CVE-2026-74045 has a CVSS score of 7.1, High severity, and lets an enrolled agent crash wazuh-analysisd with a crafted syscheck event, causing a fleet-wide detection outage. Proof-of-concept code exists for CVE-2026-74034, CVE-2026-74037, CVE-2026-74040, and CVE-2026-74045. Affected versions reach back to 3.9.0; upgrade every manager to 4.14.8.
Key Details
- Attack Vector
- Network
- Attack Complexity
- Low
- Privileges Required
- High
- User Interaction
- None
- CWE Classification
- CWE-862