# CVE-2026-39359: Wazuh Manager path traversal in authd and remoted daemons

Source: https://junglewise.ai/threats/cve-2026-39359-wazuh-manager-path-traversal-in-authd-and-remoted-daemons  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-17. Updated: 2026-07-17  
License: CC BY 4.0 with a link back

CVE-2026-39359 · Severity: high · CVSS 7.5 · Published 2026-07-17

Wazuh is a security platform used by organizations to monitor and respond to cyber threats across their infrastructure. A security flaw in the way the central manager handles new device registrations allows an attacker to trick the system into sharing sensitive internal files. This could result in the exposure of encryption keys and configuration data, potentially allowing an attacker to compromise the entire monitoring network.

Technologies: [Wazuh Manager](https://junglewise.ai/threats/technologies/wazuh-manager). Vendors: [Wazuh](https://junglewise.ai/threats/vendors/wazuh).

## Quick answers

**Is CVE-2026-39359 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-39359 being exploited in the wild.

**How severe is CVE-2026-39359?** High severity, with a CVSS score of 7.5, published 17 July 2026.

**Which products and versions are affected?** Wazuh Manager 4.0.0 - 4.10.3, 4.11.0 - 4.14.4.

**Is there a fix for CVE-2026-39359?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-39359 attacked?** It is attacked over the network, in an operating system.

**Am I affected by CVE-2026-39359?** Check whether you run Wazuh Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A logic flaw exists in the Wazuh Manager's enrollment daemon (authd) and synchronization daemon (remoted). The authd process fails to sanitize group names provided by agents during enrollment, allowing path traversal sequences like '..'. While the manager attempts to validate the group directory using wopendir(), the traversal sequence successfully resolves to the parent directory (/var/ossec/etc). Subsequently, the remoted process uses this unsanitized path to synchronize configurations, inadvertently including sensitive files such as client.keys, ossec.conf, and internal certificates in the agent's shared configuration stream. This allows an unauthenticated network attacker to exfiltrate critical secrets. The issue is fixed in versions 4.10.4 and 4.14.5.

## Affected products

- Wazuh Wazuh Manager 4.0.0 - 4.10.3, 4.11.0 - 4.14.4

## Timeline

- 2026-07-16: advisory: GitHub Security Advisory published
- 2026-07-17: disclosed: NVD publication date

## References

- [https://github.com/wazuh/wazuh/security/advisories/GHSA-6q95-fcwc-4h44](https://github.com/wazuh/wazuh/security/advisories/GHSA-6q95-fcwc-4h44)

## Related threats

- [Wazuh Manager SQL injection in WazuhDBBackend._substitute_params](https://junglewise.ai/threats/cve-2026-112341-wazuh-versions-from-4-0-0-before-4-14-9-contain-a-sql-injection)
- [Wazuh missing TLS hostname verification in fluent-forward module](https://junglewise.ai/threats/cve-2026-112339-wazuh-from-3-9-0-before-4-14-9-contains-a-missing-tls-hostname)
- [Wazuh GitHub module server-side request forgery in pagination](https://junglewise.ai/threats/cve-2026-112338-wazuh-from-4-3-0-before-4-14-9-contains-a-server-side-request)
- [Wazuh Manager memory leak in JSON decoder](https://junglewise.ai/threats/cve-2026-112336-wazuh-manager-from-3-0-0-before-4-14-9-contains-a-memory-leak)
- [Wazuh path traversal in get_list_file helper](https://junglewise.ai/threats/cve-2026-93347-wazuh-from-4-1-1-before-4-14-8-contains-a-path-traversal)