CVE-2026-74044: wazuh-manager · Path Traversal
Affects wazuh-managerSource CVE Database V5
Not known to be exploited · CVSS 7.0 High : upgrade to 4.14.6 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.14.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade wazuh-manager to 4.14.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Wazuhwazuh-manager | Affected
| Fixed in
|
GitHubwazuh-managerpkg:github/wazuh-managerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Wazuh version 4.14.6 and later. Users should upgrade to version 4.14.6 or newer to remediate this vulnerability. Until patched, restrict cluster peer access and ensure that only trusted nodes hold valid Fernet keys. Monitor for unusual cluster peer disconnections that could indicate exploitation attempts.
Description
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.