# CVE-2026-67307: Wazuh before 5.0.0-beta3 Cluster Attribution Spoofing via Inventory Sync

> A low-privileged agent can spoof cluster attribution in inventory records by forging cluster fields, potentially tampering with data or poisoning other clusters.

- **Severity:** High 7.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-jv5p-fhwh-9w55, GHSA-v7qc-fpqm-p46f

## What is CVE-2026-67307?

CVE-2026-67307 is a high-severity missing authorization vulnerability in Wazuh Wazuh, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-67307?

It affects 1 product.


Products: Wazuh Wazuh.

## How do I fix CVE-2026-67307?

No fix has been published for CVE-2026-67307 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-67307 being exploited?

There is no known exploitation of CVE-2026-67307 in the wild and no public exploit code.

## Other vulnerabilities in Wazuh Wazuh

- [CVE-2025-24016](https://insights.sbomify.com/CVE-2025-24016/): Wazuh Server Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2024-32038](https://insights.sbomify.com/CVE-2024-32038/): Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2021-44079](https://insights.sbomify.com/CVE-2021-44079/): Command injection in n/a (critical 9.8)
- [CVE-2024-1243](https://insights.sbomify.com/CVE-2024-1243/): Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft (critical 9.5)
- [CVE-2026-61800](https://insights.sbomify.com/CVE-2026-61800/): Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893) (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67307 and fix it if it is affected.

What it is: CVE-2026-67307 is a high-severity missing authorization vulnerability in Wazuh Wazuh, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67307 in the wild and no public exploit code.

Affected product: Wazuh Wazuh. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67307/ (Markdown: https://insights.sbomify.com/CVE-2026-67307/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67307
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67307
- OSV: https://osv.dev/vulnerability/CVE-2026-67307

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67307/
Summaries are generated and may contain mistakes; the official description above is the record.