CVE-2026-67307: Wazuh 5.0.0-beta1 (fixed in 5.0.0-beta3) does not validate or override the cluster_name and cluster_node field

Routine

MEDIUM 6.3DOWNGRADE

CVE-2026-67307 is a medium-severity flaw (CVSS 6.3) affecting wazuh. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 tampe

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.3 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 87%)
CISA exploited list	No
Weakness	CWE-345
Published	2026-08-01
Last modified	2026-09-01

Publisher (CNA): VulnCheck · Vendor: wazuh

Last updated 2026-09-01 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-08-01 13:17 UTCPublished CVE record published
2026-09-01 15:41 UTCUpdated Record last modified

wazuh wazuh DOWNGRADE

Affected: 5.0.0 beta1

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.0.0

1. Check installed version

apt-cache policy wazuh || rpm -q wazuh || wazuh --version

2. No fixed release: DOWNGRADE to a release before 5.0.0 (Debian / Ubuntu)

apt-cache madison wazuh sudo apt install wazuh=<VERSION_BEFORE_5.0.0> sudo apt-mark hold wazuh

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list wazuh sudo dnf downgrade wazuh-<VERSION_BEFORE_5.0.0> sudo dnf versionlock add wazuh

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-67307?

wazuh: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-67307 being exploited?

CVE-2026-67307 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-67307 affect?

CVE-2026-67307 affects wazuh. Severity is medium (CVSS 6.3). 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 al

How urgent is CVE-2026-67307?

Priority 30/100. Public exploit reference

Software pages

Wazuh vulnerabilities

Related CVEs

CVE-2026-32983 MEDIUM 5.8 UPGRADE Wazuh Manager authd service in wazuh-manager packages through version 4.7.3 contains an improper restriction o
CVE-2026-45798 HIGH 7.5 UPGRADE Wazuh is a free and open source platform used for threat prevention, detection, and response
CVE-2026-48024 CRITICAL 9.1 UPGRADE Wazuh is a free and open source platform used for threat prevention, detection, and response
CVE-2026-49441 CRITICAL 9.1 UPGRADE Wazuh is a free and open source platform used for threat prevention, detection, and response
CVE-2026-48162 CRITICAL 9.1 UPGRADE Wazuh is a free and open source platform used for threat prevention, detection, and response

References

← Back to latest CVEs