Quick answers
- Is CVE-2026-74047 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74047 being exploited in the wild.
- How severe is CVE-2026-74047?
- Medium severity, with a CVSS score of 6.5, published 13 October 2026.
- Which products and versions are affected?
- Wazuh Manager 4.0.0 to 4.14.7.
- Is there a fix for CVE-2026-74047?
- 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-74047 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-74047?
- 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
An information disclosure vulnerability in Wazuh's API allows any user holding the agent:read permission to retrieve the authd.pass enrollment password in plaintext via the agent configuration endpoint (GET /agents/000/config/auth/auth). The vulnerability exists because the mask_sensitive_config() decorator was applied only to the manager-facing configuration endpoint but not to the agent-focused endpoint, despite both querying identical underlying data. The pseudo-agent ID 000, which represents the manager itself, is incorrectly treated as a regular agent and lacks the access controls present in other sensitive methods.
Affected products
- Wazuh Wazuh Manager 4.0.0 to 4.14.7
Timeline
- 2026-10-13: disclosed