Quick answers
- Is CVE-2026-74040 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74040 being exploited in the wild.
- How severe is CVE-2026-74040?
- Critical severity, with a CVSS score of 9.1, published 13 October 2026.
- Which products and versions are affected?
- Wazuh Manager 3.9.0 before 4.14.8.
- Is there a fix for CVE-2026-74040?
- 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-74040 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-74040?
- 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 MasterHandler.process_files_from_worker function in the cluster communication layer contains two independent defects: a basename bypass of the excluded_files blocklist using trailing slashes (os.path.basename("etc/ossec.conf/") == ""), and missing direction validation allowing workers to send master-sourced files without authorization. An attacker with cluster key access can inject malicious XML into ossec.conf or agent.conf to achieve root RCE via the wodle command execution mechanism.
Affected products
- Wazuh Manager 3.9.0 before 4.14.8
Timeline
- 2026-10-13: disclosed
- 2026-09-25: patched