CVE-2026-61783 Wazuh: RBAC permission-effect check in mask_sensitive_config allows low-privilege users to read cluster.key

High 7.0 Published Updated

Low-privilege users can read sensitive cluster keys due to flawed RBAC logic that ignores deny rules when masking configuration values.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-61783?

CVE-2026-61783 is a high-severity missing authorization vulnerability in Wazuh Wazuh, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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, an authenticated low-privilege user can read the cluster secret from the manager configuration because the logic that masks sensitive values is disabled by any update-config RBAC rule, including an explicit deny. The mask_sensitive_config() decorator applies masking only when _has_update_permissions() returns false, but that gate treats a user as able to update the config whenever a  manager:update_config  or  cluster:update_config  rule exists, without ever checking whether the rule's effect is allow or deny. Because a deny rule is stored as a real entry, a read-only account that is hardened by explicitly denying config edits is counted as having update permission, which turns masking off. A single authenticated GET request to the configuration endpoint with  raw=true  then returns the verbatim ossec.conf XML with  cluster.key  in clear, whereas an otherwise identical account without the deny rule sees the value masked. This issue is fixed in version 4.14.7.

Weakness: CWE-863, CWE-200

Which versions are affected by CVE-2026-61783?

It affects 1 product.

Products include Wazuh Wazuh.

How do I fix CVE-2026-61783?

No fix has been published for CVE-2026-61783 yet. Limit exposure of the affected software until one is available.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-61783 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61783 exists.

All Wazuh Wazuh vulnerabilities

Sources

Also known as GHSA-vjcq-cf36-f5gx.

Is CVE-2026-61783 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free