CVE-2026-61802Public exploitNetwork attack vectorHinoki check available

Cluster key disclosure via missing response masking

Published Aug 27, 2026 · Updated Aug 27, 2026

Information disclosure in Wazuh 4.14.0 through 4.14.6 allows remote authenticated users to read the cluster key via a REST API request. GET /cluster/local/config calls read_config_wrapper without mask_sensitive_config, returning cluster.key in cleartext instead of redacting it. The default readonly and cluster_readonly roles satisfy the cluster:read gate; the exposed key authenticates cluster peers and enables separate peer-level attack chains.

CVSS severity6.5
Medium
EPSS probability0.41%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in Wazuh 4.14.0 through 4.14.6 allows remote authenticated users to read the cluster key via a REST API request. GET /cluster/local/config calls read_config_wrapper without mask_sensitive_config, returning cluster.key in cleartext instead of redacting it. The default readonly and cluster_readonly roles satisfy the cluster:read gate; the exposed key authenticates cluster peers and enables separate peer-level attack chains.

The record

CVE
CVE-2026-61802
Published
Aug 27, 2026
Updated
Aug 27, 2026
Vendor
Wazuh
Product
Wazuh
Classifications
CWE-522, CWE-200, T1552.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 27, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 27, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 4.14.0, < 4.14.7

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Wazuh · Wazuhversion=>= 4.14.0, < 4.14.7

Published CVSS scores

6.5GitHubCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-522Insufficiently Protected Credentials
CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1552.001Credentials In Files

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo