Root code execution via unconstrained worker file sync
Published Aug 27, 2026 · Updated Aug 27, 2026
Path traversal in Wazuh Manager 4.4.0 through 4.14.6 allows remote authenticated users to execute code as root on cluster workers. The non-merged branch of update_master_files_in_worker() uses safe_join() to stay under /var/ossec but never verifies that the destination matches its declared cluster_item_key. Holding the shared cluster key or controlling a master is required; crafted sync metadata can overwrite root-executed scripts or delete files on workers.
Summary
What happened
Path traversal in Wazuh Manager 4.4.0 through 4.14.6 allows remote authenticated users to execute code as root on cluster workers. The non-merged branch of update_master_files_in_worker() uses safe_join() to stay under /var/ossec but never verifies that the destination matches its declared cluster_item_key. Holding the shared cluster key or controlling a master is required; crafted sync metadata can overwrite root-executed scripts or delete files on workers.
The record
- CVE
- CVE-2026-61800
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- Wazuh
- Product
- Wazuh
- Classifications
- CWE-22, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 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.
- Affected versionversion=>= 4.4.0, < 4.14.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- Cluster worker non-merged sync proof of conceptproof of concept · demonstrated
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