CVE-2026-28220
Authenticated cluster peer can deserialize objects to gain admin control on Wazuh master.
Is CVE-2026-28220 being exploited?
Not confirmed. CVE-2026-28220 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-28220?
CVE-2026-28220 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-28220?
Yes. A fix has been recorded for CVE-2026-28220. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-28220 affect?
CVE-2026-28220 affects Wazuh < 4.14.5, Wazuh manager (master node), Cluster DAPI (framework/wazuh/core/cluster). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-28220?
Upgrade to Wazuh 4.14.5+, rotate cluster keys, audit API users and WAZUH_PATH files.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated actor with cluster key can bypass RBAC and execute callables to write files, create API users, modify security.yaml, and fully compromise the manager.
Immediate action required
- affected>= 4.0.0 and < 4.14.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.