Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893)
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-61800
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 19:54 UTC · Revision 1
Source evidence
Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893)
core-osv · Original sourcePublished 27 Aug 2026, 23:26 UTC
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.
osv:CVE-2026-61800
Complete source record
{
"id": "e4f895484faf105308601c0dd8169d194937c09c504a3ae04f7274f8d5d6889b",
"url": "https://osv.dev/vulnerability/CVE-2026-61800",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893)",
"summary": "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.",
"evidence": "osv:CVE-2026-61800",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2026-61800",
"aliases": [
"CVE-2026-61800",
"GHSA-3jff-488g-335f"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/wazuh/wazuh",
"type": "GIT",
"events": [
{
"introduced": "2477e9fa50bc1424e834ac8401ce2450a5978e75"
},
{
"fixed": "a42268a27c555d9348d5598fb8751eaf4c8e9024"
},
{
"fixed": "f7f7c4d2d9e683c5d42e997fe7028a3fb2578853"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.4.0"
},
{
"fixed": "4.14.7"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "f7f7c4d2d9e683c5d42e997fe7028a3fb2578853"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-61800.json"
}
}
],
"modified": "2026-10-28T02:30:23.149587446Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/61xxx/CVE-2026-61800.json",
"https://github.com/wazuh/wazuh/security/advisories/GHSA-3jff-488g-335f",
"https://nvd.nist.gov/vuln/detail/CVE-2026-61800",
"https://github.com/wazuh/wazuh/commit/f7f7c4d2d9e683c5d42e997fe7028a3fb2578853"
],
"provider_metadata": {
"cwe_ids": [
"CWE-22"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/61xxx/CVE-2026-61800.json"
}
},
"related_cves": [
{
"value": "CVE-2026-61800",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 489460,
"published_at": "2026-08-27T23:26:28.11+00:00"
}