Skip to content
major vulnerability· requires attention

Wazuh is widely used for endpoint/manager security; this RCE lets a cluster worker compromise manager and all agents, risking enterprise-wide breach and operational disruption.

Applications

CVE-2026-74040

9.4
Critical
EPSS 0.55%Patch availableOct 13, 2026

Wazuh cluster flaw lets a worker overwrite master files and achieve root RCE.

common questions

Is CVE-2026-74040 being exploited?

Not confirmed. CVE-2026-74040 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.

How severe is CVE-2026-74040?

CVE-2026-74040 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-74040?

Yes. A fix has been recorded for CVE-2026-74040. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-74040 affect?

CVE-2026-74040 affects Wazuh Manager and Agents, Wazuh versions >=3.9.0 and <4.14.8. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74040?

Upgrade to Wazuh v4.14.8+, isolate/inspect workers, rotate credentials, verify integrity.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Wazuh Manager and AgentsWazuh versions >=3.9.0 and <4.14.8
impact

A malicious or compromised cluster worker can overwrite ossec.conf and agent.conf, enabling root remote code execution on the manager and all agents.

action required

Immediate action required

affected versions
Wazuh wazuh-manager
  • affected>= 3.9.0 and < 4.14.8
vendor says fixed in4.14.8

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free