CVEvulnerability
CVE-2026-44252
7.7 HIGH
Official page ↗
- Status
- Analyzed
- Published
- 2026-08-19
- Last modified
- 2026-10-27
- Assigner
- [email protected]
- CVSS 4.0 ([email protected])
- 7.7 HIGH — CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- CVSS 3.1 ([email protected])
- 8.8 HIGH — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-863
Description
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.5, Wazuh Manager allows a low-privilege read-only API user with manager:read permission to retrieve the cluster key from the element in ossec.conf through GET /manager/configuration?raw=true. An attacker with network access to TCP port 1516 can use the disclosed Fernet key to impersonate a cluster worker and submit distributed API requests containing attacker-controlled rbac_permissions with rbac_mode set to black. Because the master trusts the worker-supplied authorization context, the attacker can create users, assign administrator roles, access credentials and API tokens, modify configuration, and execute actions across agents. This issue is fixed in version 4.14.5.
Affected configurations
• wazuh wazuh (>= 4.0.0 < 4.14.5)
Related
Weakness · CWE (1)
- CWE-863 Incorrect Authorization weakness
References
- https://github.com/wazuh/wazuh/commit/b3459f5663702aea14e91330a7a6912081fed2eb Patch
- https://github.com/wazuh/wazuh/pull/35307 Issue Tracking, Patch
- https://github.com/wazuh/wazuh/releases/tag/v4.14.5 Patch, Release Notes
- https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta3 Patch, Release Notes
- https://github.com/wazuh/wazuh/security/advisories/GHSA-34fx-c2xw-xcpg Exploit, Vendor Advisory
- https://github.com/wazuh/wazuh/security/advisories/GHSA-34fx-c2xw-xcpg Exploit, Vendor Advisory