CVE-2026-61802: Wazuh discloses cleartext cluster key to low-privilege API users via GET /cluster/local/config
Wazuh is an open-source security platform providing unified XDR and SIEM protection for endpoints and cloud workloads. In versions 4.14.0 through 4.14.6, a low-privilege API user can read the cleartext cluster key from a configuration endpoint that fails to redact it. The REST API provides a masking control, masksensitiveconfig, that redacts sensitive fields such as authd.pass and cluster.key from configuration responses for users who lack update-config permission, and every config-read endpoint carries this decorator except GET /cluster/local/config. That endpoint, backed by readconfigwrapper, is gated only by cluster:read and returns the local node's cluster configuration including the cleartext key, whereas its siblings return the same value masked. As a result, any account with the default readonly or clusterreadonly role, which is explicitly denied update-config precisely so it cannot view secrets, receives the real cluster key. Because the cluster key authenticates and encrypts traffic between cluster nodes, disclosing it to an unprivileged account provides the authentication precondition for the cluster-peer remote code execution chains established by prior advisories. This issue is fixed in version 4.14.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Wazuhto a version that resolves this vulnerability.Fixed in 4.14 - Configuration
Ensure GET /cluster/local/config responses apply the mask_sensitive_config decorator so sensitive fields including cluster.key are redacted for users lacking update-config permission.
Wazuh REST API (GET /cluster/local/config) mask_sensitive_config = enabled
Event History
Frequently Asked Questions
Which versions are affected?
Wazuh versions 4.14.0 through 4.14.6 are affected.
What access does an attacker need?
An attacker needs an authenticated API account with the cluster:read permission. They do not need update-config permission.
Are default low-privilege roles exposed?
Yes. The default readonly and cluster_readonly roles can retrieve the unmasked cluster key despite being denied update-config permission.
Why is disclosure of the cluster key significant?
The key authenticates and encrypts traffic between cluster nodes. Its disclosure provides the authentication precondition for cluster-peer remote code execution chains described by prior advisories.