CVE-2026-28220

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

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

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
57(Track*)
EG Risk 57/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
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 29, 2026

Advisory Details (1)

Auto-updated Sep 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Wazuh Cluster DAPI: arbitrary callable resolution + RBAC context injection enables cluster node to execute privileged functions on master · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-w2jj-pfq9-mh9p

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 52× 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.

Showing the most recent 100 of 104 total refreshes for this CVE.

  1. 2026-09-11 18:32 UTCEG score recompute
  2. 2026-09-11 14:52 UTCEPSS rescore
  3. 2026-09-11 09:29 UTCEG score recompute
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-09 11:56 UTCEG score recompute
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 22:55 UTCEG score recompute
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 16:55 UTCEG score recompute
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-05 19:52 UTCEG score recompute
  13. 2026-09-05 09:33 UTCEG score recompute
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-08-30 19:49 UTCEG score recompute
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 02:37 UTCEG score recompute
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-28 21:41 UTCEPSS rescore
  24. 2026-08-27 21:20 UTCEG score recompute
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 75 more
  1. 2026-08-26 22:09 UTCEG score recompute
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-25 18:43 UTCEG score recompute
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-24 18:58 UTCEG score recompute
  6. 2026-08-24 14:17 UTCEPSS rescore
  7. 2026-08-24 12:31 UTCEG score recompute
  8. 2026-08-23 01:17 UTCEG score recompute
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 03:24 UTCEG score recompute
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 01:26 UTCEG score recompute
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-19 22:50 UTCEG score recompute
  15. 2026-08-19 17:03 UTCEPSS rescore
  16. 2026-08-18 19:36 UTCEG score recompute
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 15:27 UTCEG score recompute
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-16 17:58 UTCEG score recompute
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 05:05 UTCEG score recompute
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 03:17 UTCEG score recompute
  25. 2026-08-15 01:30 UTCEPSS rescore
  26. 2026-08-14 01:27 UTCEG score recompute
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-12 14:32 UTCEG score recompute
  29. 2026-08-12 13:50 UTCEPSS rescore
  30. 2026-08-11 17:03 UTCEG score recompute
  31. 2026-08-11 13:42 UTCEPSS rescore
  32. 2026-08-11 04:10 UTCEG score recompute
  33. 2026-08-11 00:00 UTCEPSS rescore
  34. 2026-08-09 17:44 UTCEG score recompute
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-08 20:15 UTCEG score recompute
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-07 18:28 UTCEG score recompute
  39. 2026-08-06 16:40 UTCEG score recompute
  40. 2026-08-06 13:46 UTCEPSS rescore
  41. 2026-08-05 23:28 UTCEG score recompute
  42. 2026-08-05 19:17 UTCEPSS rescore
  43. 2026-08-04 17:10 UTCEG score recompute
  44. 2026-08-04 15:10 UTCEPSS rescore
  45. 2026-08-04 12:52 UTCEG score recompute
  46. 2026-08-02 06:17 UTCEG score recompute
  47. 2026-08-02 02:26 UTCEPSS rescore
  48. 2026-08-01 04:29 UTCEG score recompute
  49. 2026-08-01 04:16 UTCEPSS rescore
  50. 2026-07-30 17:52 UTCEG score recompute
  51. 2026-07-30 16:27 UTCEPSS rescore
  52. 2026-07-30 13:31 UTCEG score recompute
  53. 2026-07-30 04:49 UTCEG score recompute
  54. 2026-07-30 01:30 UTCEPSS rescore
  55. 2026-07-29 15:43 UTCEG score recompute▲ 0.70
  56. 2026-07-29 15:41 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  57. 2026-07-29 01:12 UTCEG score recompute
  58. 2026-07-28 15:36 UTCEPSS rescore
  59. 2026-07-28 00:22 UTCEG score recompute
  60. 2026-07-26 23:14 UTCEG score recompute
  61. 2026-07-26 14:54 UTCEPSS rescore
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-26 10:48 UTCEG score recompute
  64. 2026-07-25 14:18 UTCEPSS rescore
  65. 2026-07-25 14:17 UTCEPSS rescore
  66. 2026-07-24 14:17 UTCEPSS rescore
  67. 2026-07-23 14:18 UTCEPSS rescore
  68. 2026-07-23 14:18 UTCEPSS rescore
  69. 2026-07-23 03:08 UTCEG score recompute
  70. 2026-07-22 23:38 UTCEG score recompute
  71. 2026-07-22 14:08 UTCEPSS rescore
  72. 2026-07-22 14:08 UTCEPSS rescore
  73. 2026-07-21 15:24 UTCEPSS rescore
  74. 2026-07-21 15:24 UTCEPSS rescore
  75. 2026-07-20 19:07 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-28220?
CVE-2026-28220 is a critical vulnerability published on July 20, 2026. 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…
When was CVE-2026-28220 disclosed?
CVE-2026-28220 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-28220 actively exploited?
CVE-2026-28220 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 66.9% of all scored CVEs.
What is the CVSS score of CVE-2026-28220?
CVE-2026-28220 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-28220?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28220, 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-28220

Explore →

Is Your Infrastructure Affected by CVE-2026-28220?

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

Start Free Scan →Browse All CVEs