Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
Wazuh is a free and open source platform used for threat prevention, detection, and response. Prior to version 4.14.5, issues in the Cluster Distributed API (DAPI) handling allow a cluster peer, or any actor able to authenticate to the cluster channel using the shared cluster key, to make the master node deserialize an attacker-controlled callable and execute it under an attacker-controlled RBAC context. The cluster code in `framework/wazuh/core/cluster/common.py` deserializes JSON with `as_wazuh_object()`, which resolves any callable whose top-level package is wazuh or api (an overly broad allowlist controlled only by `ALLOWED_CALLABLES_PACKAGES`), and DAPI requests handled in framework/wazuh/core/cluster/dapi/dapi.py accept a client-supplied rbac_permissions value that `run_local()` applies as the global RBAC context, so supplying an rbac_mode of black causes authorization checks for expose_resources-protected functions to pass without any legitimate permission assignment. Combined, these allow privileged administrative actions on the master node such as arbitrary file writes under WAZUH_PATH, creation of new API users, and tampering with security.yaml, and can be chained into full manager compromise. This issue has been fixed in version 4.14.5.
Priority
LOW
Exploitation
NONE
PoC
YES
Patch
AVAILABLE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
| Date | Total | Labels |
|---|
| 2026-07-20 | 2 | Disclosure1General1 |
| 2026-08-13 | 1 | Patch1 |
| 2026-08-14 | 1 | Disclosure1 |
CVE-2026-28220 Wazuh is a free and open source platform used for threat prevention, detection, and response. Prior to version 4.14.5, issues in the Cluster Distributed API (DAPI) ha… https://www.cve.org/CVERecord?id=CVE-2026-28220
Post summary
The entry merely cites CVE-2026-28220 and notes a DAPI issue in Wazuh before version 4.14.5, with no further technical, exploit, or mitigation information.
Wazuh のクラスタ機能に任意コード実行の脆弱性を追加しました。CVSS 8.4 ですが、要件は AV:A と PR:H です。クラスタを有効にしていなければこの経路自体が存在しないので、まず ossec.conf の cluster 設定を確認するところからになります。 https://cve.autoarticles.net/cve/CVE-2026-28220
Post summary
The post announces an arbitrary code execution vulnerability in Wazuh’s cluster feature (CVSS 8.4, AV:A, PR:H) and advises checking the ossec.conf cluster setting to mitigate the issue.
🔒 #CyberSecurity CVE-2026-28220: Wazuh Cluster DAPI Deserialization RCE (CVSS 9.9) — Detection a… "Wazuh occupies a privileged position in most environments: it sees everything, talks to…" 🔗 https://securityarsenal.com/blog/cve-2026-28220-wazuh-cluster-dapi-deserialization-rce-cvss-99-detection-and-remediation-guide #CyberSecurity #ThreatIntel #critical #zeroday #cve
Post summary
CVE‑2026‑28220 is a high‑severity deserialization RCE affecting Wazuh Cluster DAPI, and the post links to a remediation guide that outlines how to mitigate the threat.
🚨 HIGH - Wazuh Cluster DAPI RBAC bypass via callable deserialization (CVE-2026-28220) In Wazuh before 4.14.5, flaws in the Cluster Distributed API (DAPI) request handling allow attacker-controlled callables to be deserialized and executed on the master node under an attacker-chosen RBAC context. The root cause is unsafe deserialization combined with improper authorization enforcement due to an overly broad callable allowlist and client-controlled RBAC fields (including an rbac_mode of black). An attacker can exploit this as an authenticated cluster peer or anyone who obtains the shared cluster key by sending crafted DAPI messages that bypass authorization checks. Impact includes privileged administrative actions on the master (arbitrary file writes under WAZUH_PATH, creating new API users, tampering with security.yaml), potentially escalating to full Wazuh manager compromise. 👉 Affected: wazuh < 4.14.5 | Upgrade to 4.14.5
Post summary
A high‑severity flaw (CVE‑2026‑28220) in Wazuh versions before 4.14.5 permits attackers to deserialize arbitrary callables under an attacker‑chosen RBAC context, enabling privileged execution; upgrading to 4.14.5 resolves the issue.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | wazuh | wazuh | - | - | - |