Security readout for executives and security teams
Plain-English summary
An attacker who obtains a Wazuh cluster key can manipulate files on affected worker nodes, potentially taking full root control. The flaw is critical because Wazuh is itself a security platform, so compromise could disrupt monitoring, alter security data, and affect protected systems.
Executive priority
Treat affected clustered deployments as an immediate remediation priority, especially where cluster-key confidentiality is uncertain. Upgrade promptly and investigate suspicious /var/ossec changes. There is no supplied evidence of active exploitation, but successful abuse could provide root control and undermine security monitoring.
Technical view
Wazuh 4.4.0 through 4.14.6 incompletely validates destinations during non-merged worker file synchronization. Paths remain beneath /var/ossec but can escape the directory assigned by cluster_item_key, enabling authenticated cluster peers to write, overwrite, or delete sensitive files and potentially execute code as root. Version 4.14.7 fixes the issue.
Likely exposure
Exposure applies to Wazuh clusters containing worker nodes running versions 4.4.0 through 4.14.6. Exploitation requires possession of the cluster key and access to cluster synchronization. Risk is greatest where that key is shared broadly, exposed, or available on a compromised cluster peer.
Exploitation context
The CVSS score is 9.1. Exploitation has low complexity and requires no user interaction, but requires the cluster key, reflected as high privileges. The supplied sources provide no evidence of active exploitation, and the CVE is not listed as KEV.
Researcher notes
This is an incomplete fix for CVE-2026-30893. safe_join() prevents traversal outside /var/ossec but does not enforce the destination associated with cluster_item_key. The missing check affects the worker's non-merged update and deletion paths; equivalent validation existed elsewhere. The supplied commit and advisory document the 4.14.7 correction.
Mitigation direction
- Upgrade affected Wazuh managers and worker nodes to version 4.14.7 or later using vendor guidance.
- Prioritize clusters where the cluster key may have been disclosed, shared broadly, or stored insecurely.
- Rotate the cluster key if compromise is suspected, then monitor cluster behavior and file integrity.
- Restrict cluster connectivity to trusted nodes while remediation is pending.
Validation and detection
- Inventory Wazuh versions and identify clustered deployments containing worker nodes.
- Confirm every affected cluster node reports version 4.14.7 or later.
- Review logs and file-integrity data for unexpected changes or deletions beneath /var/ossec.
- Investigate unauthorized changes to files under /var/ossec that execute with root privileges.
- Review cluster-key access and distribution for unexpected exposure.
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-61800 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.
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.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wazuh/wazuh/security/advisories/GHSA-3jff-488g-335fCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/wazuh/wazuh/commit/f7f7c4d2d9e683c5d42e997fe7028a3fb2578853CVE 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.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.