Quick answers
- Is CVE-2026-74033 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74033 being exploited in the wild.
- How severe is CVE-2026-74033?
- Medium severity, with a CVSS score of 6.1, 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-74033?
- 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-74033 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-74033?
- 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_lists() and delete_list_file() functions in the CDB list handlers fail to validate that file paths remain within the intended USER_LISTS_PATH directory. These functions are reachable through the internal cluster RPC mechanism, which bypasses REST/OpenAPI validation and RBAC checks. An attacker with a compromised worker node can send absolute or traversal paths to read arbitrary files (via get_lists()) or delete files anywhere under WAZUH_PATH (via delete_list_file()), including critical files like rbac.db, without authentication or authorization.
Affected products
- Wazuh Wazuh Manager 4.1.1 to before 4.14.8
Timeline
- 2026-10-13: disclosed
- 2026-09-25: patched