CVE-2026-49441Public exploitNetwork attack vectorHinoki check available

Authenticated file overwrite via unchecked file_path

Published Aug 19, 2026 · Updated Aug 19, 2026

Arbitrary file write in Wazuh before 4.14.6 and before 5.0.0-beta3 allows remote authenticated users to overwrite files via cluster sync metadata. In the non-merged branch of process_files_from_worker() in framework/wazuh/core/cluster/master.py, the manager uses the peer-controlled file_path key from files_metadata.json as the destination under WAZUH_PATH and moves the uploaded archive entry there without checking that the resolved path stays within the directory selected by cluster_item_key. Exploitation requires control of a cluster peer and the shared Fernet key, and overwriting etc/ossec.conf can configure root-executed commands and reach code execution after a service reload.

CVSS severity9.1
Critical
EPSS probability0.52%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Arbitrary file write in Wazuh before 4.14.6 and before 5.0.0-beta3 allows remote authenticated users to overwrite files via cluster sync metadata. In the non-merged branch of process_files_from_worker() in framework/wazuh/core/cluster/master.py, the manager uses the peer-controlled file_path key from files_metadata.json as the destination under WAZUH_PATH and moves the uploaded archive entry there without checking that the resolved path stays within the directory selected by cluster_item_key. Exploitation requires control of a cluster peer and the shared Fernet key, and overwriting etc/ossec.conf can configure root-executed commands and reach code execution after a service reload.

The record

CVE
CVE-2026-49441
Published
Aug 19, 2026
Updated
Aug 19, 2026
Vendor
Wazuh
Product
Wazuh
Classifications
CWE-73
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 4.3.0, < 4.14.6
  2. Affected versionversion=>= 5.0.0-beta1, < 5.0.0-beta3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Wazuh · Wazuhversion=>= 4.3.0, < 4.14.6; version=>= 5.0.0-beta1, < 5.0.0-beta3

Published CVSS scores

9.1GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-73External Control of File Name or Path

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo