Wazuh
CVE-2026-39359
HIGH
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-reachable enrollment with no auth in default config (PR:N, AV:N, AC:L); impact is disclosure of sensitive config files only, so C:H, I:N, A:N.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
2DescriptionCVE.org
Wazuh is a free and open source platform used for threat prevention, detection, and response. In versions 4.0.0 through 4.10.3 and 4.11.0 through 4.14.4, a logic flaw affects the Wazuh Manager's enrollment daemon (authd) and synchronization daemon (remoted). The authd process allows agents to select a group during enrollment but does not filter path traversal sequences such as "..." While the manager checks for the group directory using wopendir(), the ".." sequence references the parent directory (/var/ossec/etc), allowing it to pass validation. After the malicious group is accepted and stored in the manager's global database, the remoted process uses this unchecked value to build paths for agent configuration synchronization. As a result, sensitive files from /var/ossec/etc, such as client.keys, ossec.conf, and internal certificates, are included in the agent's shared configuration stream and exposed to the attacker. This issue has been fixed in versions 4.10.4 and 4.14.5.
AnalysisAI
Sensitive file disclosure in the Wazuh Manager (versions 4.0.0-4.10.3 and 4.11.0-4.14.4) allows a malicious enrolling agent to exfiltrate manager secrets by abusing the group parameter during enrollment. The authd enrollment daemon fails to filter path traversal ("..") sequences in the agent-selected group name, so remoted later builds shared-configuration paths that reach /var/ossec/etc and stream files such as client.keys, ossec.conf, and internal certificates to the attacker-controlled agent. There is no public exploit identified at time of analysis, but the network-reachable, unauthenticated CVSS 7.5 profile makes this a meaningful confidentiality risk for exposed manager enrollment services.
Technical ContextAI
Wazuh is an open-source security platform (SIEM/XDR/HIDS) whose Manager coordinates fleets of endpoint agents. Two Manager components are implicated: authd, the enrollment daemon that registers new agents and lets them request a configuration group, and remoted, the daemon that pushes shared/group configuration back to agents. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / path traversal): authd validates the requested group by opening the group directory with wopendir(), but a ".." component resolves to the parent directory (/var/ossec/etc) and therefore passes the existence check instead of being rejected. Because the tainted group value is persisted to the Manager's global database and later concatenated into filesystem paths by remoted without re-validation, the traversal converts a directory-existence check into arbitrary read of files under the Wazuh configuration tree.
RemediationAI
Vendor-released patch: upgrade the Wazuh Manager to 4.10.4 (for the 4.10.x line) or 4.14.5 (for the 4.11.0-4.14.4 line), per the advisory at https://github.com/wazuh/wazuh/security/advisories/GHSA-6q95-fcwc-4h44. Until patched, restrict network exposure of the enrollment service by firewalling the authd port (default TCP 1515) so only trusted provisioning networks can reach it, and enable authd enrollment password authentication (use_password) to prevent unauthenticated agents from registering - the trade-off is added operational overhead when onboarding new agents. Because client.keys and internal certificates may have been exposed, treat this as a potential secrets-compromise event: after patching, rotate agent keys and re-issue affected certificates, accepting the cost of re-enrolling agents. Monitor Manager logs for enrollment requests containing group names with ".." sequences as a detection measure.
Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t
In the wazuh-slack active response script in Wazuh 4.2.x before 4.2.5, untrusted user agents are passed to a curl comman
Path-traversal-driven root code execution affects the Wazuh security platform's cluster synchronization layer in version
Arbitrary file read in Wazuh cluster deployments (4.0.0 through 4.14.5, and 5.0.0-beta1/beta2) lets a peer node that alr
Arbitrary file write leading to root remote code execution affects Wazuh worker nodes in clustered deployments running v
A critical deserialization vulnerability in Wazuh's cluster mode allows attackers with access to any worker node to achi
Remote code execution on the Wazuh cluster master node is achievable by any attacker who controls a cluster worker node,
Path traversal in Wazuh's ip-customblock active response script allows low-privileged remote attackers to create or dele
The agent in OSSEC through 3.1.0 on Windows allows local users to gain NT AUTHORITY\SYSTEM access via Directory Traversa
Cluster key disclosure in Wazuh Manager versions 4.0.0 through 4.14.4 enables a two-stage privilege escalation: a low-pr
Arbitrary file deletion on a Wazuh manager via the cluster synchronization protocol allows a cluster-authenticated attac
CVE-2024-1243 is an improper input validation vulnerability in Wazuh agent for Windows (versions prior to 4.8.0) that al
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today