CVE-2026-61800: Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893)

Published Aug 27, 2026
·
Updated

Wazuh is an open-source security platform providing unified XDR and SIEM protection for endpoints and cloud workloads. In versions 4.4.0 through 4.14.6, a party holding the cluster key can write, overwrite, or delete arbitrary files under /var/ossec on worker nodes, leading to remote code execution as root. During cluster file synchronization, the non-merged branch of updatemasterfilesinworker() moves each staged file to a destination derived only from safejoin(), which confines the path to /var/ossec but never verifies that the file lands in the directory declared by its clusteritemkey. Because the destination check present on the primary node and on the worker's merged branch was not applied, a peer can place files at attacker-chosen locations under /var/ossec, including paths that are executed as root, and the delete branch has the same gap. This is an incomplete fix for CVE-2026-30893, which addressed traversal outside /var/ossec but left this path able to redirect files anywhere within it. This issue is fixed in version 4.14.7.

Affected Software

1 affected component
Wazuh Wazuh>=4.4.0<=4.14.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Wazuh to a version that resolves this vulnerability.

    Fixed in 4.14.7
  2. Operational

    After upgrading to version 4.14.7, review /var/ossec for any attacker-written, overwritten, or deleted files on worker nodes and restore expected contents if changes are found.

Event History

Aug 27, 2026
CVE Published
via MITRE·11:26 PM
Data Sourced
via MITRE·11:26 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Wazuh versions 4.4.0 through 4.14.6 are affected. The issue applies to cluster worker nodes during cluster file synchronization.

2

What level of access does an attacker need?

An attacker must possess the Wazuh cluster key. No user interaction is required.

3

What is the impact on a compromised worker?

A cluster peer holding the key can write, overwrite, or delete arbitrary files anywhere under /var/ossec on worker nodes. This can lead to remote code execution as root by placing files in locations executed with root privileges.

4

How can I remediate this issue?

Upgrade Wazuh to version 4.14.7, which fixes the issue. Systems running versions 4.4.0 through 4.14.6 should be treated as affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203