CVE-2026-44252: Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.5…
CVE-2026-44252 · Severity: high · CVSS 8.8 · Published 2026-08-19
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.
No. Junglewise Threat Intelligence has no report of CVE-2026-44252 being exploited in the wild.
How severe is CVE-2026-44252?
High severity, with a CVSS score of 8.8, published 19 August 2026.
Which products and versions are affected?
Wazuh. The advisory does not name versions.
Is there a fix for CVE-2026-44252?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-44252?
Check whether you run Wazuh. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.