Skip to main content
Vulnerability Database/CVE-2026-74036

CVE-2026-74036: Wazuh Security Platform RCE Vulnerability

CVE-2026-74036 is a remote code execution flaw in Wazuh Security Platform versions 4.3.0 to 4.14.7 that allows attackers controlling a manager to execute commands as root on agents. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-74036 Overview

CVE-2026-74036 is a remote code execution vulnerability in Wazuh affecting versions 4.3.0 through 4.14.7. The flaw resides in the Security Configuration Assessment (SCA) subsystem, which determines policy trust based on file path rather than configuration source. An attacker who controls a Wazuh manager can write unsigned policy files to the var/incoming directory through the upgrade channel. Agents accept these files as trusted and execute arbitrary command checks as root. The vulnerability is classified under CWE-863: Incorrect Authorization.

Critical Impact

Attackers with manager access can execute arbitrary commands as root on every connected Wazuh agent, enabling full fleet compromise from a single pivot point.

Affected Products

  • Wazuh 4.3.0 through 4.14.7
  • Wazuh Manager (policy distribution component)
  • Wazuh Agent (SCA policy execution component)

Discovery Timeline

  • 2026-10-13 - CVE-2026-74036 published to NVD
  • 2026-10-15 - Last updated in NVD database

Technical Details for CVE-2026-74036

Vulnerability Analysis

Wazuh's Security Configuration Assessment module runs policy files that define system compliance checks. Some policy checks use command directives, which execute shell commands on the agent with root privileges. To prevent abuse, Wazuh signs trusted policies shipped by the vendor and rejects unsigned policies that attempt command execution.

The vulnerability stems from how the agent evaluates trust. Rather than tracking whether a policy came from a signed source or an attacker-controlled channel, the agent inspects the file system path where the policy resides. Files placed in certain paths are treated as trusted. The var/incoming directory, used for the manager-to-agent upgrade channel, is one such trusted location.

An attacker who compromises or controls a Wazuh manager can write a malicious SCA policy file into var/incoming on agents via the upgrade channel. The agent then references and executes the unsigned policy, running arbitrary command checks as root.

Root Cause

The root cause is an authorization decision based on file location instead of cryptographic signature or configuration source. The SCA trust model conflates file path with provenance, allowing any writer to the trusted path to bypass policy signing requirements.

Attack Vector

Exploitation requires high privileges on a Wazuh manager. Once an attacker controls the manager, they stage a crafted policy file containing command checks and push it to agents through the upgrade channel. Agents place the file in var/incoming, treat it as trusted, and execute the embedded commands as root during the next SCA scan cycle. No agent-side user interaction is required.

Refer to the GitHub Security Advisory GHSA-qmhg-366r-jjfp and the VulnCheck Wazuh Remote Code Execution Advisory for additional technical details.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-74036

Indicators of Compromise

  • Unexpected policy files written to the var/incoming directory on Wazuh agents
  • SCA scan results referencing policy identifiers not shipped by Wazuh or defined in agent configuration
  • Child processes of the Wazuh agent executing shell commands, interpreters, or network utilities as root
  • Upgrade channel activity from a manager outside normal maintenance windows

Detection Strategies

  • Monitor file creation and modification events in var/incoming and other SCA policy directories on agents
  • Alert on Wazuh agent processes spawning children that are not part of normal SCA baseline checks
  • Correlate manager-initiated upgrade events with subsequent SCA policy additions on agents
  • Review SCA scan logs for policy filenames that do not match the vendor's signed policy catalog

Monitoring Recommendations

  • Enable file integrity monitoring on all Wazuh agent configuration and policy directories
  • Centralize Wazuh agent and manager logs to a SIEM for cross-fleet anomaly detection
  • Track privileged process execution lineage on hosts running Wazuh agents
  • Audit administrative access to Wazuh managers and alert on unauthorized logins

How to Mitigate CVE-2026-74036

Immediate Actions Required

  • Upgrade all Wazuh managers and agents to version 4.14.8 or later
  • Audit Wazuh manager accounts and remove unused or stale administrative access
  • Inspect var/incoming on all agents for unexpected policy files and remove them
  • Review recent SCA scan results for signs of attacker-controlled command execution

Patch Information

Wazuh addressed the vulnerability in version 4.14.8. The fix enforces policy trust based on signing and configuration source rather than file path. Download the patched release from the GitHub Wazuh Release v4.14.8 page and follow the vendor's upgrade documentation for coordinated manager-and-agent rollout.

Workarounds

  • Restrict network access to Wazuh manager administrative interfaces using firewall rules and network segmentation
  • Enforce strong authentication and least-privilege access for all Wazuh manager accounts
  • Monitor and alert on writes to var/incoming and other SCA-trusted paths until patching is complete
  • Disable the SCA module on agents if patching cannot be performed immediately and the module is not required
bash
# Verify Wazuh agent version after upgrade
/var/ossec/bin/wazuh-control info | grep WAZUH_VERSION

# List any unexpected policy files staged by the upgrade channel
ls -la /var/ossec/var/incoming/

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.