CVE-2026-67307Network attack vectorHinoki check available

Cluster attribution spoofing via trusted inventory metadata

Published Aug 1, 2026 · Updated Aug 1, 2026

Data integrity failure in Wazuh 5.0.0-beta1 allows remote authenticated users to spoof cluster attribution through inventory sync. The manager validates Start.agentid against the enrolled agent identity but copies agent-controlled cluster_name and cluster_node values into trusted session context used for document fields and identifiers. A valid enrolled-agent credential is sufficient to forge indexed cluster metadata; cross-cluster record poisoning also requires a shared indexer and colliding numeric agent IDs.

CVSS severity7.0
High
EPSS probability0.19%
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

Data integrity failure in Wazuh 5.0.0-beta1 allows remote authenticated users to spoof cluster attribution through inventory sync. The manager validates Start.agentid against the enrolled agent identity but copies agent-controlled cluster_name and cluster_node values into trusted session context used for document fields and identifiers. A valid enrolled-agent credential is sufficient to forge indexed cluster metadata; cross-cluster record poisoning also requires a shared indexer and colliding numeric agent IDs.

The record

CVE
CVE-2026-67307
Published
Aug 1, 2026
Updated
Aug 1, 2026
Vendor
Wazuh
Product
Wazuh
Classifications
CWE-639, CWE-345, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 1, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 1, 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=0 <5.0.0-beta3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Wazuh · Wazuhversion=0 <5.0.0-beta3

Published CVSS scores

6.3WazuhCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N
6.3VulnCheck CNACVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N
7.0VulnCheck CNACVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA: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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key
CWE-345Insufficient Verification of Data Authenticity
T1565.001Stored Data Manipulation

Public exploit references

No public exploit references are available in this record.

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