# CVE-2026-93347: Wazuh path traversal in get_list_file helper

Source: https://junglewise.ai/threats/cve-2026-93347-wazuh-from-4-1-1-before-4-14-8-contains-a-path-traversal  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-13. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-93347 · Severity: medium · CVSS 4.9 · Published 2026-10-13

Wazuh is a security monitoring and threat detection platform used by enterprises to collect and analyze logs from across their infrastructure. A flaw in the cluster communication layer allows a compromised cluster worker to read sensitive files on the manager, including authentication keys and configuration files containing cluster secrets. An attacker with the cluster key could extract credentials and compromise the security of the entire Wazuh infrastructure.

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

## Quick answers

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

**How severe is CVE-2026-93347?** Medium severity, with a CVSS score of 4.9, published 13 October 2026.

**Which products and versions are affected?** Wazuh Manager 4.1.1 to before 4.14.8.

**Is there a fix for CVE-2026-93347?** Yes: fixed in 4.14.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-93347 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-93347?** 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.

## How to fix

- Fixed in 4.14.8

## Technical details

The get_list_file cluster-callable helper function constructs file paths from attacker-supplied filenames without path traversal validation, allowing directory traversal sequences like "../" to escape the intended USER_LISTS_PATH directory. The function is reachable via the DistributedAPI cluster transport, bypassing REST API controls. An attacker with the cluster key can read arbitrary files as the wazuh user, including client.keys, ossec.conf, and API secrets.

## Affected products

- Wazuh Wazuh Manager 4.1.1 to before 4.14.8

## Timeline

- 2026-10-13: disclosed

## References

- [https://github.com/wazuh/wazuh/releases/tag/v4.14.8](https://github.com/wazuh/wazuh/releases/tag/v4.14.8)
- [https://github.com/wazuh/wazuh/security/advisories/GHSA-xrjw-cqrv-j92g](https://github.com/wazuh/wazuh/security/advisories/GHSA-xrjw-cqrv-j92g)

## 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 API login throttling race condition](https://junglewise.ai/threats/cve-2026-93346-wazuh-from-4-0-0-before-4-14-8-contains-a-race-condition-in-api)