External risk intelligence

Wazuh Agent NTLM Relay Privilege Escalation Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2025-30201

The vulnerability affects the Wazuh Agent, which is typically deployed as a background service on internal endpoints and servers. While the agent communicates with a central manager over a network, it is not an internet-facing service or edge gateway, and direct public exposure is uncommon in standard deployments.

Remote Code Execution

Wazuh

before 4.13.0

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in the Wazuh Agent, an open-source platform for threat detection, could allow authenticated attackers to exploit NTLM authentication to escalate privileges and execute remote code. This issue has been addressed in version 4.13.0. The main concern at this time is to confirm if this specific technology is in use and if so, assess its exposure.

  • Allows attackers to gain system control.
  • Potentially serious security control bypass.
  • Confirm use and evaluate exposure.

Attack Path

How an attacker could exploit the issue

An attacker with existing privileged access to a Wazuh agent can initiate a connection to a malicious server by crafting specific configuration settings. This allows the attacker to trick the agent into authenticating to their controlled server using NTLM. If successful, this can lead to privilege escalation or remote code execution on the affected system.

  • Requires authenticated agent access.
  • Triggers NTLM authentication via UNC paths.
  • Leads to privilege escalation and RCE.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, authenticated attackers could force NTLM authentication through malicious UNC paths in Wazuh Agent configurations. This could lead to NTLM relay attacks that escalate privileges and allow remote code execution on affected systems.

  • Wazuh agent authentication credentials.

-Malicious UNC paths in agent configurations. -Privilege escalation and remote code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Action for this CVE advisory primarily falls to teams managing Wazuh deployments, which may include security operations, infrastructure, or platform engineering. The initial practical step is to identify all systems running the affected Wazuh Agent, confirm their business criticality and network exposure, and then engage the accountable owners to plan remediation.

  • Platform or Security Operations teams own this.
  • Verify agent deployment and network reachability.
  • Plan phased upgrades during maintenance windows.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Wazuh and what does its agent do?

Wazuh is an open-source security platform designed for threat detection, prevention, and response. The Wazuh agent is a software component installed on endpoints and servers to collect security data, monitor system integrity, and report activity back to a central management server to help organizations secure their infrastructure.

What does CVE-2025-30201 mean by NTLM relay?

This vulnerability involves 'CWE-73: External Control of File Name or Path' and 'CWE-294: Authentication Bypass by Capture-replay'. It means an attacker can provide a malicious file path to the agent, forcing it to try connecting to an attacker-controlled server using NTLM authentication. The attacker then intercepts and relays that authentication data to gain unauthorized access or run commands with higher privileges.

How is this CVE-2025-30201 vulnerability triggered?

The flaw requires an attacker to already have authenticated access to the Wazuh agent, allowing them to modify specific configuration settings. By injecting a malicious UNC path into those settings, they trigger the agent to attempt an external NTLM connection. Simply running the agent or connecting it to a legitimate manager does not trigger the vulnerability; it requires intentional, malicious configuration changes.

Do I need to worry about this if my Wazuh agents are internal?

According to Halo Surface Signal, this vulnerability is considered 'Unlikely' to be directly accessible from the internet because Wazuh agents typically operate as background services within internal networks. However, because the attack requires existing authenticated access, any user or system capable of modifying the agent's configuration settings poses a potential risk regardless of network placement.

How should I respond to this vulnerability?

The primary response is to update all instances of the Wazuh Agent to version 4.13.0 or later, as this release includes the necessary patch. Start by inventorying your environment to identify every system running older versions, prioritize those with higher business criticality, and coordinate with your platform or security teams to schedule the upgrades during your next maintenance window.

References