CVE-2026-67307

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-01. a secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.3
EG Score
6.3(high)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 3, 2026

Advisory Details (3)

Auto-updated Aug 1, 2026
Patch available. Sources: github, github_commit.
generic

Wazuh before 5.0.0-beta3 Cluster Attribution Spoofing via Inventory Sync | Advisories | VulnCheck

https://www.vulncheck.com/advisories/wazuh-before-beta3-cluster-attribution-spoofing-via-inventory-sync
github_commit Patch Available

commit b3dae02ec9dd (wazuh/wazuh)

Patch available: wazuh/wazuh v5.0.0-beta3 (contains commit b3dae02ec9dd)

https://github.com/wazuh/wazuh/commit/b3dae02ec9ddcfd449cb61b4c76d180e3e43f79a
github Patch Available

Enrolled Agent Can Spoof Cluster Attribution in Inventory Sync Documents · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-jv5p-fhwh-9w55

Vendor Advisories for CVE-2026-67307(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 14:22 UTCEG score recompute
  2. 2026-08-20 14:22 UTCGHSA enrichment
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-19 11:43 UTCEG score recompute
  5. 2026-08-19 11:43 UTCGHSA enrichment
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-18 10:38 UTCEG score recompute
  8. 2026-08-18 10:38 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 09:33 UTCEG score recompute
  11. 2026-08-17 09:33 UTCGHSA enrichment
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 08:29 UTCEG score recompute
  14. 2026-08-16 08:29 UTCGHSA enrichment
  15. 2026-08-15 07:25 UTCEG score recompute
  16. 2026-08-15 07:25 UTCGHSA enrichment
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 06:20 UTCGHSA enrichment
  19. 2026-08-13 05:15 UTCEG score recompute
  20. 2026-08-13 05:15 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-12 04:11 UTCEG score recompute
  23. 2026-08-12 04:11 UTCGHSA enrichment
  24. 2026-08-11 03:06 UTCEG score recompute
  25. 2026-08-11 03:06 UTCGHSA enrichment
Show 32 more
  1. 2026-08-11 00:00 UTCEPSS rescore
  2. 2026-08-10 02:01 UTCEG score recompute
  3. 2026-08-10 02:01 UTCGHSA enrichment
  4. 2026-08-09 13:47 UTCEPSS rescore
  5. 2026-08-09 00:57 UTCEG score recompute
  6. 2026-08-09 00:57 UTCGHSA enrichment
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-07 23:52 UTCEG score recompute
  9. 2026-08-07 23:52 UTCGHSA enrichment
  10. 2026-08-06 22:48 UTCEG score recompute
  11. 2026-08-06 22:47 UTCGHSA enrichment
  12. 2026-08-06 13:47 UTCEPSS rescore
  13. 2026-08-05 21:32 UTCEG score recompute
  14. 2026-08-05 21:32 UTCGHSA enrichment
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-04 20:28 UTCEG score recompute
  18. 2026-08-04 20:27 UTCGHSA enrichment
  19. 2026-08-04 15:10 UTCEPSS rescore
  20. 2026-08-04 10:39 UTCEPSS rescore
  21. 2026-08-03 19:19 UTCEG score recompute
  22. 2026-08-03 19:19 UTCGHSA enrichment
  23. 2026-08-03 19:05 UTCEG score recompute
  24. 2026-08-03 19:05 UTCGHSA enrichment
  25. 2026-08-03 15:27 UTCEG score recompute
  26. 2026-08-03 15:27 UTCGHSA enrichment
  27. 2026-08-03 10:36 UTCEPSS rescore
  28. 2026-08-02 14:23 UTCEG score recompute
  29. 2026-08-02 14:23 UTCGHSA enrichment
  30. 2026-08-01 13:18 UTCEG score recompute
  31. 2026-08-01 12:43 UTCEG score recompute
  32. 2026-08-01 12:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-67307?
CVE-2026-67307 is a medium vulnerability published on August 1, 2026. Wazuh 5.0.0-beta1 (fixed in 5.0.0-beta3) does not validate or override the clustername and clusternode 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…
When was CVE-2026-67307 disclosed?
CVE-2026-67307 was first published in the National Vulnerability Database on August 1, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67307 actively exploited?
CVE-2026-67307 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.3% of all scored CVEs.
What is the CVSS score of CVE-2026-67307?
CVE-2026-67307 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-67307?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67307, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-67307

Explore →

Is Your Infrastructure Affected by CVE-2026-67307?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs