CVE-2026-49441
Received Received - Intake

Path Traversal in Wazuh Leading to Remote Code Execution

Publication date: 2026-08-19

Last updated on: 2026-08-19

Assigner: GitHub, Inc.

Description
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.3.0 until 4.14.6 and 5.0.0-beta3, the non-merged branch of process_files_from_worker() in framework/wazuh/core/cluster/master.py trusts a peer-controlled file_path key from files_metadata.json. The destination is joined to WAZUH_PATH without proving that it remains inside the directory selected by cluster_item_key. A cluster peer holding the shared Fernet key can upload a crafted extra-valid archive and overwrite security-sensitive files such as /var/ossec/etc/ossec.conf. Replacing ossec.conf can configure root-executed commands and lead to code execution after a service reload. This issue is fixed in versions 4.14.6 and 5.0.0-beta3.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-19
Last Modified
2026-08-19
Generated
2026-08-19
AI Q&A
2026-08-19
EPSS Evaluated
N/A
NVD
CVE-2026-49441
EUVD
EUVD-2026-62571

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
wazuh wazuh From 4.3.0 (inc) to 4.14.6 (inc)
wazuh wazuh 5.0.0-beta3
wazuh wazuh 4.14.6

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-73 The product allows user input to control or influence paths or file names that are used in filesystem operations.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Wazuh allows a cluster peer with access to the Fernet key to exploit improper file path validation in the cluster synchronization process. The issue occurs in the non-merged branch of process_files_from_worker() where a peer-controlled file_path key from files_metadata.json is trusted without validation. This enables overwriting arbitrary files within the WAZUH_PATH directory, including critical files like /var/ossec/etc/ossec.conf.

Detection Guidance

Check Wazuh manager versions between 4.3.0 and 4.14.6 or 5.0.0-beta3. Inspect cluster logs for unauthorized file writes or suspicious metadata.json files in WAZUH_PATH. Look for unexpected changes in /var/ossec/etc/ossec.conf or other critical files.

Impact Analysis

An attacker could exploit this to overwrite security-sensitive files such as ossec.conf, leading to root-executed commands and remote code execution after a service reload. This could allow full system compromise, rule/decoder injection, CDB list poisoning, or configuration overrides in the Wazuh environment.

Compliance Impact

This vulnerability could lead to unauthorized access, data breaches, or system compromise, violating compliance requirements for data protection and security controls in standards like GDPR and HIPAA. Unauthorized file modifications may expose sensitive data or disrupt critical security configurations.

Mitigation Strategies

Upgrade Wazuh to version 4.14.6 or later immediately. Restrict Fernet key access to trusted cluster peers only. Monitor for unauthorized file modifications in WAZUH_PATH directories.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-49441. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart