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

> An attacker with the cluster key can write arbitrary files under /var/ossec on worker nodes, leading to remote code execution as root.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-3jff-488g-335f

## What is CVE-2026-61800?

CVE-2026-61800 is a critical path traversal vulnerability in Wazuh Wazuh, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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 update_master_files_in_worker() moves each staged file to a destination derived only from safe_join(), which confines the path to /var/ossec but never verifies that the file lands in the directory declared by its cluster_item_key. 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-61800?

It affects 1 product.


Products: Wazuh Wazuh.

## How do I fix CVE-2026-61800?

No fix has been published for CVE-2026-61800 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61800 being exploited?

There is no known exploitation of CVE-2026-61800 in the wild and no public exploit code.

## Other vulnerabilities in Wazuh Wazuh

- [CVE-2025-24016](https://insights.sbomify.com/CVE-2025-24016/): Wazuh Server Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2024-32038](https://insights.sbomify.com/CVE-2024-32038/): Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2021-44079](https://insights.sbomify.com/CVE-2021-44079/): Command injection in n/a (critical 9.8)
- [CVE-2024-1243](https://insights.sbomify.com/CVE-2024-1243/): Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft (critical 9.5)
- [CVE-2026-48024](https://insights.sbomify.com/CVE-2026-48024/): Wazuh: merged-file header path traversal in cluster sync allows arbitrary file write under WAZUH_PATH in Wazuh manager (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61800 and fix it if it is affected.

What it is: CVE-2026-61800 is a critical path traversal vulnerability in Wazuh Wazuh, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61800 in the wild and no public exploit code.

Affected product: Wazuh Wazuh. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61800/ (Markdown: https://insights.sbomify.com/CVE-2026-61800/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61800
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61800
- OSV: https://osv.dev/vulnerability/CVE-2026-61800

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61800/
Summaries are generated and may contain mistakes; the official description above is the record.