CVE-2026-61802 wazuh CVE debrief

Who should care

Roles with cluster:read permission, such as those with the default readonly or cluster_readonly role, should assess their exposure and prioritize upgrading to version 4.14.7 or later.

Why it matters

A low-privilege API user can read the cleartext cluster key from a configuration endpoint in Wazuh versions 4.14.0 through 4.14.6, providing the authentication precondition for remote code execution chains.

• Disclosing the cluster key provides the authentication precondition for remote code execution chains.
• An attacker with the cluster key can authenticate and encrypt traffic between cluster nodes.
• Defenders should verify exposure and prioritize upgrading to version 4.14.7 or later.

Technical summary

The REST API provides a masking control, mask_sensitive_config, that redacts sensitive fields such as authd.pass and cluster.key from configuration responses for users who lack update-config permission. However, the GET /cluster/local/config endpoint fails to redact the cleartext cluster key, allowing low-privilege API users to read it. This issue is fixed in version 4.14.7. The cluster key authenticates and encrypts traffic between cluster nodes, and disclosing it to an unprivileged account provides the authentication precondition for remote code execution chains.

Defensive priority

Defenders should prioritize verifying exposure and upgrading to version 4.14.7 or later. Roles with cluster:read permission, such as those with the default readonly or cluster_readonly role, should assess their exposure.

Recommended defensive actions

• Verify exposure by checking if the Wazuh version is between 4.14.0 and 4.14.6.
• Upgrade to version 4.14.7 or later.
• Restrict cluster:read permission to only necessary roles.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the issue. A patch is available in version 4.14.7. The REST API provides a masking control, mask_sensitive_config, that redacts sensitive fields such as authd.pass and cluster.key from configuration responses for users who lack update-config permission. However, the GET /cluster/local/config endpoint fails to redact the cleartext cluster key, allowing low-privilege API users to read it. Evidence limits suggest verifying exposure and prioritizing upgrading to 4.14.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.