CVE-2026-44252
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.5% in the next 30 days (EPSS).
- Severity: 7.7 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.5% · EPSS, next 30 days
- Weakness
- CWE-863 · Incorrect authorization
- Record status
- Analyzed
Affected
- Wazuh < 4.14.5
Attack profile CVSS 4.0 · 7.7
- Attack vector
- Network
- Complexity
- Low
- Attack requirements
- Present
- Privileges needed
- Low
- User interaction
- None
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
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
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-44252.md and follow it. Check whether this project is affected by CVE-2026-44252. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/wazuh/wazuh/commit/b3459f5663702aea14e91330a7a6912081fed2eb
- https://github.com/wazuh/wazuh/pull/35307
- https://github.com/wazuh/wazuh/releases/tag/v4.14.5
- https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta3
- https://github.com/wazuh/wazuh/security/advisories/GHSA-34fx-c2xw-xcpg
- https://github.com/wazuh/wazuh/security/advisories/GHSA-34fx-c2xw-xcpg
References
- https://github.com/wazuh/wazuh/commit/b3459f5663702aea14e91330a7a6912081fed2eb
- https://github.com/wazuh/wazuh/pull/35307
- https://github.com/wazuh/wazuh/releases/tag/v4.14.5
- https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta3
- https://github.com/wazuh/wazuh/security/advisories/GHSA-34fx-c2xw-xcpg
- https://github.com/wazuh/wazuh/security/advisories/GHSA-34fx-c2xw-xcpg