Security readout for executives and security teams
Plain-English summary
A trusted Wazuh cluster peer possessing the shared Fernet key can overwrite sensitive manager files. Altering the main configuration may enable commands to run as root after a service reload, potentially compromising the manager and its security operations.
Executive priority
Treat this as an urgent manager upgrade, especially where cluster credentials may be exposed or peer trust is uncertain. Compromise could undermine the security platform itself and enable root-level execution, although the attacker must already possess privileged cluster access.
Technical view
The non-merged processing branch trusts a peer-supplied file_path from files_metadata.json without confirming the destination remains within the cluster item directory. This permits arbitrary file writes under WAZUH_PATH, including ossec.conf. The affected ranges are 4.3.0 through 4.14.5 and 5.0.0-beta1 through beta2.
Likely exposure
Exposure is limited to affected Wazuh managers where an attacker controls a cluster peer and possesses the shared Fernet key. This is not described as an unauthenticated internet attack, but compromised peer credentials or cluster membership could produce manager-level impact.
Exploitation context
The bundle reports no CISA KEV listing, and the cited sources provide no evidence of active exploitation. Exploitation requires privileged cluster access through a peer holding the shared Fernet key. Successful configuration replacement can lead to root-level code execution after reload.
Researcher notes
The issue is CWE-73 path control in process_files_from_worker(). The vulnerable non-merged branch fails to constrain peer-controlled metadata to the directory selected by cluster_item_key. The documented impact is arbitrary overwrite under WAZUH_PATH; evidence does not establish writes outside that root.
Mitigation direction
- Upgrade stable Wazuh installations to version 4.14.6 or later.
- Upgrade Wazuh 5.0 beta installations to 5.0.0-beta3 or later.
- Protect the shared Fernet key and restrict cluster participation to authorized peers.
- Review the vendor advisory and release guidance before applying changes.
Validation and detection
- Inventory every Wazuh manager and flag versions within the affected ranges.
- Confirm all stable managers run 4.14.6 or later.
- Confirm all 5.0 beta managers run beta3 or later.
- Review cluster peer membership and shared-key access for unauthorized holders.
- Inspect ossec.conf and other sensitive WAZUH_PATH files for unexpected changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-49441 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wazuh/wazuh/security/advisories/GHSA-3v57-hgvj-3vj2CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/wazuh/wazuh/pull/36296CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/wazuh/wazuh/commit/7f13682cf5f01f69452f723a608ab2d89cfb2133CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/wazuh/wazuh/releases/tag/v4.14.6CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta3CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.