Vulnerability in Wazuh (CVE-2026-67307)
Summary
Vulnerability in Wazuh (CVE-2026-67307). Data can be tampered with by attackers. Mitigation: upgrade to 5.0.0-beta3 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-67307 has been found in Wazuh.
Data can be tampered with by attackers. CVSS score: 6.3/10.
What to do: upgrade Wazuh to 5.0.0-beta3 or later.
If unsure, ask your IT team or search "Wazuh CVE-2026-67307" on the vendor's site.
CVE-2026-67307 (Wazuh) — CWE-345 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.0.0-beta3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-345) exists in Wazuh.
Check the vendor advisory for the affected versions of Wazuh.
Severity: Medium (CVSS 6.3/10). Data can be tampered with by attackers.
Update to 5.0.0-beta3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Wazuh' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Wazuh' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Wazuhを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Wazuh to 5.0.0-beta3ステージング環境で 5.0.0-beta3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit disclosure@vulncheck.com
- exploit disclosure@vulncheck.com
- patch disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com