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