CVE-2026-67307

Wazuh before 5.0.0-beta3 Cluster Attribution Spoofing via Inventory Sync

Published Aug 1, 2026 CVSS 4.0 · 7 High EPSS < 1% KEV · Not listed
Description
Wazuh 5.0.0-beta1 (fixed in 5.0.0-beta3) does not validate or override the cluster_name and cluster_node fields in inventory-sync Start FlatBuffer messages, while validating only the agentid against the authenticated agent identity. This allows a low-privileged enrolled agent to spoof cluster attribution in indexed inventory and vulnerability documents by forging wazuh.cluster.name values and influencing the document _id prefix, potentially tampering with inventory records or, in shared-indexer multi-cluster deployments, poisoning another cluster's records when numeric agent IDs collide.

Analysis

AI-generated

Technical impact

A low‑privileged agent enrolled in a Wazuh cluster can forge the cluster_name and cluster_node fields in inventory‑sync Start FlatBuffer messages. The system only checks the agentid against the authenticated identity, so an attacker can spoof cluster attribution. This vulnerability allows an attacker to alter indexed inventory and vulnerability documents, potentially corrupting inventory records for their own cluster or poisoning another cluster’s records when numeric agent IDs collide. The weakness is a form of improper input validation, specifically CWE‑345.

Affected Systems

The issue affects Wazuh deployments running before version 5.0.0‑beta3. Versions 5.0.0‑beta1 and 5.0.0‑beta2 are vulnerable. The fix is available in 5.0.0‑beta3 and later releases. The affected product is the Wazuh agent and manager services that participate in cluster inventory synchronization.

Risk and Exploitability

The CVSS base score is 7, indicating a high severity condition. The EPSS score is not provided, so the current exploitation probability is unclear, but the vulnerability is actively used in shared‑indexer multi‑cluster environments and is not reported in the CISA KEV catalog. The likely attack vector is an authenticated agent that can send crafted inventory‑sync messages, underscoring that the threat is exploitable by any user with enrollment rights in the cluster.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Wazuh 5.0.0‑beta3 or any newer release that includes the fix for cluster_name and cluster_node validation.
  • If an upgrade is not immediately possible, isolate the cluster by disabling or tightly restricting inventory‑sync traffic and ensure that only trusted, unique agent IDs are allowed to communicate with the indexer.
  • Configure monitoring to detect anomalous cluster_name values in inventory documents and review any records that were created during the affected period for potential tampering.

Generated by OpenCVE AI on August 2, 2026 at 03:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:wazuh:wazuh:5.0.0:beta1:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Wazuh 5.0.0-beta1 (fixed in 5.0.0-beta3) does not validate or override the cluster_name and cluster_node fields in inventory-sync Start FlatBuffer messages, while validating only the agentid against the authenticated agent identity. This allows a low-privileged enrolled agent to spoof cluster attribution in indexed inventory and vulnerability documents by forging wazuh.cluster.name values and influencing the document _id prefix, potentially tampering with inventory records or, in shared-indexer multi-cluster deployments, poisoning another cluster's records when numeric agent IDs collide.
Title Wazuh before 5.0.0-beta3 Cluster Attribution Spoofing via Inventory Sync
First Time appeared Wazuh
Wazuh wazuh
Weaknesses CWE-345
CPEs cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*
Vendors & Products Wazuh
Wazuh wazuh
References
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N'}

cvssV4_0

{'score': 7, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 3, 2026, 6:35 PM
Reserved
Jul 29, 2026, 1:04 PM
Status
Analyzed
Published
Aug 1, 2026, 1:17 PM
Modified
Sep 1, 2026, 3:41 PM