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… (CVE-2026-67307)
Wazuh 5.0.0-beta1 contains a vulnerability where the cluster_name and cluster_node fields in inventory-sync Start FlatBuffer messages are not validated or overridden. This allows a low-privileged enrolled agent to spoof cluster attribution in indexed inventory and vulnerability documents by forging wazuh.cluster.name values. The flaw can lead to tampering with inventory records or poisoning of another cluster's records in shared-indexer multi-cluster deployments when numeric agent IDs collide. The issue was fixed in version 5.0.0-beta3.
AI Analysis
Technical Summary
The vulnerability in Wazuh 5.0.0-beta1 arises because the cluster_name and cluster_node fields in inventory-sync Start FlatBuffer messages are not properly validated or overridden, while only the agentid is validated against the authenticated agent identity. This allows a low-privileged enrolled agent to spoof cluster attribution by forging wazuh.cluster.name values, influencing the document _id prefix in indexed inventory and vulnerability documents. In multi-cluster deployments using shared indexers, this can result in poisoning of another cluster's records if numeric agent IDs collide. The vulnerability is tracked as CVE-2026-67307 and is classified under CWE-345 (Insufficient Verification of Data Authenticity).
Potential Impact
An attacker with low privileges as an enrolled agent can spoof cluster attribution in inventory and vulnerability documents, potentially tampering with inventory records. In shared-indexer multi-cluster environments, this can lead to cross-cluster data poisoning when numeric agent IDs collide. The vulnerability does not impact confidentiality or availability but has a high impact on data integrity within the Wazuh monitoring infrastructure.
Mitigation Recommendations
This vulnerability is fixed in Wazuh version 5.0.0-beta3. Users should upgrade to version 5.0.0-beta3 or later to remediate this issue. No other mitigation or temporary workaround is indicated in the available data.
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… (CVE-2026-67307)
Description
Wazuh 5.0.0-beta1 contains a vulnerability where the cluster_name and cluster_node fields in inventory-sync Start FlatBuffer messages are not validated or overridden. This allows a low-privileged enrolled agent to spoof cluster attribution in indexed inventory and vulnerability documents by forging wazuh.cluster.name values. The flaw can lead to tampering with inventory records or poisoning of another cluster's records in shared-indexer multi-cluster deployments when numeric agent IDs collide. The issue was fixed in version 5.0.0-beta3.
CVSS v3.1
Score 6.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Wazuh 5.0.0-beta1 arises because the cluster_name and cluster_node fields in inventory-sync Start FlatBuffer messages are not properly validated or overridden, while only the agentid is validated against the authenticated agent identity. This allows a low-privileged enrolled agent to spoof cluster attribution by forging wazuh.cluster.name values, influencing the document _id prefix in indexed inventory and vulnerability documents. In multi-cluster deployments using shared indexers, this can result in poisoning of another cluster's records if numeric agent IDs collide. The vulnerability is tracked as CVE-2026-67307 and is classified under CWE-345 (Insufficient Verification of Data Authenticity).
Potential Impact
An attacker with low privileges as an enrolled agent can spoof cluster attribution in inventory and vulnerability documents, potentially tampering with inventory records. In shared-indexer multi-cluster environments, this can lead to cross-cluster data poisoning when numeric agent IDs collide. The vulnerability does not impact confidentiality or availability but has a high impact on data integrity within the Wazuh monitoring infrastructure.
Mitigation Recommendations
This vulnerability is fixed in Wazuh version 5.0.0-beta3. Users should upgrade to version 5.0.0-beta3 or later to remediate this issue. No other mitigation or temporary workaround is indicated in the available data.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-v7qc-fpqm-p46f
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-67307"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6e6293bf32cb7a344f68d6
Added to database: 08/01/2026, 21:18:11 UTC
Last enriched: 08/01/2026, 21:21:23 UTC
Last updated: 08/02/2026, 03:01:42 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.