Skip to content
Connect AISign inSign up free
CVE-2026-494419.1CriticalCWE-73

CVE-2026-49441: Wazuh : peer-controlled metadata key in process_files_from_worker non-merged branch allows arbitrary file write under WAZUH_PATH on Wazuh manager

wazuh

No fix listed · Affected: wazuh · Exploitation: not established

ExploitationNot established

Not in CISA KEV as of catalogue 2026.11.13 (13 Nov)

  1. In CISA KEV: not seen
  2. Exploited (reported): not seen
  3. Scanning observed: not seen
  4. Proof of concept public: not seen
  5. Not establishedNothing in the sources we check
0.8%probability of exploitation in the next 30 days
56th percentile
050100

Higher than 56% of scored CVEs

9.1CriticalCVSS 3.1
LowCrit.

DescriptionNVD

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
wazuh
Published
August 2026

Coverage1 article · 1 outlet

First in our coverage: SecurityOnline, 11 Aug.

  1. Critical Wazuh Flaws Allow Root Access via Cluster Key
    SecurityOnline · first in our coverage

New articles also arrive in the RSS feed.

References