# CVE-2026-74043: Wazuh path traversal in cluster upload functions

Source: https://junglewise.ai/threats/cve-2026-74043-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-74043 · Severity: critical · CVSS 9 · Published 2026-10-13

Wazuh, a security monitoring and threat detection platform, contains a path traversal vulnerability in its cluster file-upload functions that allows attackers with the cluster key to write files anywhere on the system as the wazuh user. By sending specially crafted upload requests through the cluster API with path traversal sequences (like ../), an attacker can bypass validation and write arbitrary files, potentially leading to remote code execution when combined with other system features.

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

## Quick answers

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

**How severe is CVE-2026-74043?** Critical severity, with a CVSS score of 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-74043?** 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-74043 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-74043?** 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 upload_list_file, upload_rule_file, and upload_decoder_file functions build destination paths from caller-supplied filenames with no traversal validation at the framework layer; validation exists only in the REST API controller. An attacker with cluster credentials can invoke these functions via DistributedAPI requests that bypass the controller's validation layer, using ../ sequences in the filename parameter to write files outside intended directories. The vulnerability stems from incomplete fixes to CVE-2026-25770 that addressed receive_file but not these related upload functions, and requires possession of the cluster key.

## Affected products

- 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-cw26-jj8q-x7w5](https://github.com/wazuh/wazuh/security/advisories/GHSA-cw26-jj8q-x7w5)

## 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)