# CVE-2026-74047: Wazuh information disclosure via agent config endpoint

Source: https://junglewise.ai/threats/cve-2026-74047-wazuh-from-4-0-0-before-4-14-8-contains-an-information-disclosure  
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-74047 · Severity: medium · CVSS 6.5 · Published 2026-10-13

Wazuh, a security monitoring and threat detection platform, exposes the agent enrollment password to low-privileged users through an API endpoint. An attacker with the default read-only role can retrieve the plaintext enrollment secret and use it to register unauthorized agents with the manager, gaining a foothold for data falsification or lateral movement across monitored infrastructure.

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

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

## 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-qj8j-r988-54rx](https://github.com/wazuh/wazuh/security/advisories/GHSA-qj8j-r988-54rx)

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