Wazuh up to 4.14.5/5.0.0-beta2 DistributedAPI dapi.py DistributedAPI.send_tmp_file path traversal

Summaryinfo

A vulnerability has been found in Wazuh up to 4.14.5/5.0.0-beta2 and classified as very critical. This issue affects the function DistributedAPI.send_tmp_file of the file framework/wazuh/core/cluster/dapi/dapi.py of the component DistributedAPI. The manipulation of the argument tmp_file leads to path traversal. This vulnerability is documented as CVE-2026-48162. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as very critical, has been found in Wazuh up to 4.14.5/5.0.0-beta2. This issue affects the function DistributedAPI.send_tmp_file of the file framework/wazuh/core/cluster/dapi/dapi.py of the component DistributedAPI. The manipulation of the argument tmp_file with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-48162 since 05/21/2026. The exploitation is known to be easy. The attack may be initiated remotely. The exploitation needs additional levels of successful authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/19/2026). MITRE ATT&CK project uses the attack technique T1006 for this issue.

Upgrading to version 4.14.6 or 5.0.0-beta3 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Wazuh

Version

• 4.14.0
• 4.14.1
• 4.14.2
• 4.14.3
• 4.14.4
• 4.14.5
• 5.0.0-beta1
• 5.0.0-beta2

Website

• Product: https://github.com/wazuh/wazuh/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion