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

Unknown severity · Source severity not reportedCVE-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

Answer in brief

CVE-2026-49441 records a Unknown severity vulnerability in Wazuh : peer-controlled metadata key in process_files_from_worker non-merged branch allows arbitrary file write under WAZUH_PATH on Wazuh manager. The current sources do not mark it as known exploited. The current feed maps wazuh/wazuh (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 19, 2026Updated Aug 19, 2026Source checked Aug 19, 2026First seen by HOL Aug 19, 2026Material review Aug 19, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps wazuh/wazuh (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
wazuh/wazuhgeneric	>= 4.3.0, < 4.14.6 \|\| >= 5.0.0-beta1, < 5.0.0-beta3	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for wazuh/wazuh.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 19, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.