Is CVE-2026-61802 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-61802 being exploited in the wild.

How severe is CVE-2026-61802?

Medium severity, with a CVSS score of 6.5, published 28 August 2026.

Which products and versions are affected?

Wazuh Manager 4.14.0 through 4.14.6.

Is there a fix for CVE-2026-61802?

A patch was published on 2026-08-28: Fixed in version 4.14.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-61802 attacked?

It is attacked over the network.

Am I affected by CVE-2026-61802?

Check whether you run Wazuh or 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.

CVE-2026-61802: Wazuh cluster key disclosure in GET /cluster/local/config

CVE-2026-61802 · Severity: medium · CVSS 6.5 · Published 2026-08-28

Wazuh is an open-source security platform that protects enterprise endpoints and cloud infrastructure through centralized threat detection and response. A flaw in the REST API allows low-privilege users with read-only roles to retrieve the cleartext cluster authentication key from a configuration endpoint that should redact it. An attacker with this key can impersonate cluster nodes and execute remote code as root across the entire Wazuh cluster, compromising all monitored assets.

Technologies: Wazuh, Wazuh Manager. Vendors: Wazuh.

Quick answers

Is CVE-2026-61802 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-61802 being exploited in the wild.
How severe is CVE-2026-61802?: Medium severity, with a CVSS score of 6.5, published 28 August 2026.
Which products and versions are affected?: Wazuh Manager 4.14.0 through 4.14.6.
Is there a fix for CVE-2026-61802?: A patch was published on 2026-08-28: Fixed in version 4.14.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-61802 attacked?: It is attacked over the network.
Am I affected by CVE-2026-61802?: Check whether you run Wazuh or 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.

Technical details

The vulnerability is a missing security decorator (mask_sensitive_config) on the GET /cluster/local/config endpoint in the REST API. While sibling endpoints like GET /manager/configuration properly mask sensitive fields including the cluster.key for read-only users, the cluster local config endpoint returns the cleartext key unmasked. The root cause is that framework/wazuh/cluster.py imports and uses only expose_resources and async_list_handler, omitting the mask_sensitive_config import needed to redact secrets. An authenticated API user with the default readonly or cluster_readonly role (which explicitly lacks update-config permission) can retrieve the 32-character cluster pre-shared key via network request with no special preconditions. Possession of this key, combined with network access to the cluster port (default 1516), enables authentication as a cluster peer, fulfilling the prerequisite for documented Critical RCE chains (GHSA-m8rw-v4f6-8787, GHSA-r4f7-v3p6-79jm, CVE-2026-25769/25770/30893) that grant root code execution. The patch applies the missing @mask_sensitive_config decorator to the vulnerable endpoint.

Affected products

Wazuh Wazuh Manager 4.14.0 through 4.14.6

Timeline

2026-08-28: disclosed
2026-08-28: patched: Fixed in version 4.14.7

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.