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. From 4.0.0 until 4.14.6 and 5.0.0-beta3, DistributedAPI.send_tmp_file() in framework/wazuh/core/cluster/dapi/dapi.py joins an attacker-controlled tmp_file value to WAZUH_PATH without canonicalization or confinement. A cluster peer holding the shared Fernet key can use traversal or an absolute path to make the master return any readable file over the cluster channel. Reading /var/ossec/api/configuration/security/private_key.pem allows the peer to forge administrator REST API tokens offline and then exercise administrative privileges without creating an account. This issue is fixed in versions 4.14.6 and 5.0.0-beta3.
Priority
LOW
Exploitation
NONE
PoC
YES
Patch
AVAILABLE
Momentum
NONE
If you run products in this scope, you should treat this CVE as relevant to your environment.
1 version affected across 1 product
Warning: Critical #vulnerabilities in #Wazuh! CVE-2026-49441, CVE-2026-48024, CVE-2026-48162 (CVSS 9.1). Cluster peers can overwrite configs or forge admin tokens, risking code execution with root privileges! Time to #Patch #Patch #Patch
Post summary
The tweet alerts users to critical Wazuh CVEs that enable config tampering or token forging leading to root code execution, urging quick patching.
3 of 3 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | wazuh | wazuh | - | - | - |
| App | wazuh | wazuh | 5.0.0 | - | - |
| App | wazuh | wazuh | 5.0.0 | - | - |