Security readout for executives and security teams
Plain-English summary
A trusted or compromised Wazuh cluster peer possessing the shared cluster key can escape intended synchronization directories and overwrite manager files. Overwriting configuration may introduce commands executed as root after services reload, potentially compromising the Wazuh manager and disrupting security monitoring.
Executive priority
Treat as an urgent remediation for affected clustered deployments, especially where peer trust or key custody is uncertain. The access prerequisite reduces broad internet exposure, but compromise could grant root-level control over a central security-management system. Prioritize version verification and upgrade without waiting for exploitation evidence.
Technical view
In affected releases, cluster.unmerge_info() builds paths from peer-controlled merged-archive metadata, while process_files_from_worker() insufficiently confines writes to the declared cluster item directory. Traversal can write beneath WAZUH_PATH, including ossec.conf. Malicious configuration changes may produce root-level code execution upon service reload.
Likely exposure
Exposure applies to Wazuh clusters running 4.0.0 through 4.14.5 or 5.0.0-beta1 through beta2. Exploitation requires a cluster peer with the shared Fernet key. The supplied sources do not describe standalone deployments as affected through another path.
Exploitation context
No active exploitation is established by the supplied sources, and the CVE is not identified as being in KEV. The prerequisite is significant but realistic after compromise of a trusted cluster peer or disclosure of the shared Fernet key. Successful exploitation could escalate to root-level execution.
Researcher notes
The critical boundary failure spans merged-file path construction and master-side write confinement. Relevant inputs are merge_type, name, files_metadata.json, and merged-file headers. Analysis should focus on canonical path validation and enforcement at the final write boundary. The supplied evidence establishes impact and fixes, but not active exploitation.
Mitigation direction
- Upgrade affected 4.x deployments to Wazuh 4.14.6 or later.
- Upgrade affected 5.0 beta deployments to 5.0.0-beta3 or later.
- Apply the fixed version consistently across relevant cluster systems.
- Consult the Wazuh advisory for deployment-specific upgrade and operational guidance.
Validation and detection
- Inventory Wazuh manager and cluster-peer versions against the affected ranges.
- Confirm every relevant 4.x system runs 4.14.6 or later.
- Confirm every relevant 5.0 beta system runs beta3 or later.
- Review cluster membership and access to the shared Fernet key.
- Investigate unexpected changes to ossec.conf and other files beneath WAZUH_PATH.
- Review service reloads and subsequent privileged activity for suspicious behavior.
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-22: 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-48024 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-gh4h-fx78-q8xcCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/wazuh/wazuh/pull/36204CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/wazuh/wazuh/commit/88fc89fdfb1bf37b9d826e9c281a3d22655733deCVE 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.