CVE-2026-93347 is a path traversal vulnerability in Wazuh wazuh-manager versions from 4.1.1 up to but not including 4.14.8. It allows malicious cluster workers with the cluster key to read arbitrary files by sending specially crafted DistributedAPI requests with unvalidated filenames. This can expose sensitive files such as client.keys and ossec.conf. The vulnerability is fixed in version 4.14.8.
CVE-2026-93346 is a vulnerability in Wazuh wazuh-manager versions 4.0.0 up to but not including 4.14.8. It involves a race condition in the API login throttling mechanism that allows unauthenticated attackers to bypass the maximum login attempt limits by sending concurrent login requests. This enables attackers to perform unlimited password guessing attacks against the authenticate and run_as endpoints. The issue is fixed in version 4.14.8.
Wazuh Manager versions from 4.0.0 up to but not including 4.14.8 have an information disclosure vulnerability. Low-privileged users with the agent:read permission can access the plaintext enrollment password via an unmasked agent configuration endpoint. This allows attackers with the default readonly role to retrieve the authd.pass secret for a pseudo-agent ID 000 and potentially enroll rogue agents against the manager. The vulnerability is fixed in version 4.14.8.
CVE-2026-74045 is a heap-based buffer overflow vulnerability in Wazuh wazuh-manager versions from 3.12.0 up to but not including 4.14.8. The flaw occurs in the fim_generate_alert() function where a buffer is allocated based on input size but written with a size bounded by OS_MAXSTR, leading to heap corruption. An enrolled agent can exploit this by sending a crafted FIM syscheck event, causing the wazuh-analysisd process to crash and resulting in a fleet-wide detection outage. The vulnerability has a high severity score of 7.1 and was fixed in version 4.14.8.
CVE-2026-74043 is a path traversal vulnerability in Wazuh wazuh-manager versions from 4.1.1 up to but not including 4.14.8. It allows malicious cluster workers who possess the cluster key to write files to arbitrary paths by sending specially crafted DistributedAPI requests with '../' sequences in filenames. This bypasses REST controller validation and enables writing files as the wazuh user. The vulnerability is fixed in version 4.14.8.
CVE-2026-74041 is a high-severity vulnerability in Wazuh wazuh-manager versions 4.14.3 through before 4.14.8 and 4.10.4 through before 4.10.5. It involves a case-sensitivity mismatch between the ossec.conf validator and the wazuh-logcollector component, allowing authenticated users with the manager:update_config privilege to inject an uppercase LOG_FORMAT command. This command is executed by the collector with root privileges upon reload, bypassing remote-command validation.
CVE-2026-74040 is a critical vulnerability in Wazuh wazuh-manager versions 3.9.0 up to but not including 4.14.8. It allows a cluster worker to overwrite protected master files due to missing authorization checks and a basename bypass. This can lead to root remote code execution on the manager and all connected agents. The issue is fixed in version 4.14.8.
Wazuh wazuh-manager versions from 4.0.0 up to but not including 4.14.8 have a vulnerability where issued tokens for run_as users with zero static roles are not properly invalidated. This occurs because the token validation process does not check the blacklist, allowing attackers with revoked administrator privileges to continue authenticating and escalate their privileges permanently. The issue is fixed in version 4.14.8.
Wazuh wazuh-manager versions from 4.6.0 up to but not including 4.14.8 contain an authentication bypass vulnerability. This flaw allows a delegated user administrator to bypass the reserved user guard by sending an empty password to the user update endpoint, enabling takeover of the wazuh superuser account and authentication with empty credentials. The vulnerability is fixed in version 4.14.8.
CVE-2026-74034 is a high-severity vulnerability in Wazuh wazuh-manager versions 4.1.0 up to but not including 4.14.8. It involves a missing origin check in the wm_agent_upgrade functionality, allowing enrolled agents to issue upgrade_custom commands with attacker-controlled file paths. This flaw enables attackers to read arbitrary files as root, including sensitive files like /etc/shadow and client.keys, potentially leading to credential exposure.
CVE-2026-74033 is a path traversal vulnerability in Wazuh wazuh-manager versions from 4.1.1 up to but not including 4.14.8. It affects the internal cluster RPC path handlers get_lists() and delete_list_file(), allowing compromised cluster workers to bypass REST validation and RBAC controls. This enables attackers to read or delete sensitive master files such as rbac.db. The vulnerability is fixed in version 4.14.8.
CVE-2026-74032 is an authorization bypass vulnerability in Wazuh wazuh-manager versions 4.0.0 through before 4.14.8. It allows low-privileged authenticated users to access unprotected security endpoints that expose the RBAC catalog. Specifically, attackers can query GET /security/actions and /security/resources endpoints, which do not enforce RBAC policies, enabling them to map privileged actions and endpoints. This information can be used to plan privilege escalation attacks. The vulnerability has a medium severity score of 5.3 and was fixed in version 4.14.8.
CVE-2026-74031 is a path traversal vulnerability in Wazuh wazuh-manager versions 4.1.1 through before 4.14.8. It allows malicious cluster workers with the cluster key to delete arbitrary files by exploiting unvalidated filename parameters in delete_rule_file and delete_decoder_file helpers. This can lead to deletion of critical configuration files such as ossec.conf, client.keys, or rules as the wazuh user. The vulnerability is fixed in version 4.14.8.
Wazuh from 3.9.0 before 4.14.8 contains an uncontrolled YAML alias expansion vulnerability in yaml2json_node that allows a manager-controlled policy to exhaust agent memory. Attackers controlling the manager can push a small SCA policy with nested aliases via merged.mg to OOM-kill wazuh-modulesd on every agent in a group.
Wazuh 4.4.0 before 4.14.7 contains a denial of service vulnerability in the fdecompress_files() function within cluster.py that allows authenticated cluster peers to exhaust memory by supplying a malicious synchronization archive without decompressed size limits. Attackers holding a valid cluster Fernet key can upload a small, highly compressed zip bomb archive that forces wazuh-clusterd on the master node to decompress the full payload into memory, causing memory exhaustion and service disruption.
Wazuh 4.0.0 before 4.14.6 contains a path traversal vulnerability that allows authenticated cluster peers to delete arbitrary directory contents by supplying a traversal-shaped node name in the cluster hello payload without validation. Attackers holding a valid cluster Fernet key can craft a malicious node name and disconnect, triggering the master's peer cleanup routine to remove the contents of arbitrary directories within the Wazuh installation path writable by the wazuh user.
Wazuh 4.0.0 before 4.14.7 and 5.0.0-beta2 contain a denial of service vulnerability that allows authenticated attackers with allow_run_as enabled to exhaust CPU resources by submitting arbitrarily deeply nested JSON structures to the POST /security/user/authenticate/run_as endpoint. Attackers can repeatedly submit malformed auth_context bodies with unlimited nesting depth to cause the API framework to consume excessive CPU, denying service to all other API consumers.
Wazuh 4.0.0 before 4.14.6 contains a path traversal vulnerability that allows unauthenticated remote attackers to cause denial of service by enrolling an agent with a dot-sequence name such as ".." through the enrollment port. Attackers exploit insufficient validation in OS_IsValidName() and unsafe path concatenation in delete_diff() to resolve the traversal to the parent queue directory, causing its subdirectories to be removed and stopping all Wazuh services requiring manual recovery.