CVE-2026-93347

4.9Medium

Published 13 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash

4.9Medium

Attack vector: Network
Complexity: Low
Privileges needed: High
User interaction: None
Impact: High impact on confidentiality
Weakness: CWE-22

Impact

An attacker with valid cluster credentials can read arbitrary files owned by the Wazuh process, including client.keys and ossec.conf. They must already compromise a cluster worker or hold the shared cluster key to send DistributedAPI requests.

Root cause

The get_list_file helper fails to sanitize filename inputs, allowing path traversal sequences.

Affected systems

Wazuh 4.1.1 before 4.14.8

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Fix & remediation

Upgrade Wazuh manager instances to version 4.14.8 or later. If patching immediately is not possible, restrict cluster network communication (port 1516 by default) to trusted worker nodes only and rotate the cluster key if compromise is suspected.

shell

$ sudo apt-get update && sudo apt-get install --only-upgrade wazuh-manager

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

Wazuh from 4.1.1 before 4.14.8 contains a path traversal vulnerability in the get_list_file helper that allows malicious cluster workers to read arbitrary files via unvalidated filename values. Attackers holding the cluster key can send DistributedAPI requests with traversal filenames to read client.keys, ossec.conf with the cluster key, and other wazuh-readable files.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-93347