Wazuh: merged-file header path traversal in cluster sync allows arbitrary file write under WAZUH_PATH in Wazuh manager
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta3, cluster.unmerge_info() in framework/wazuh/core/cluster/cluster.py constructs paths from peer-controlled merge_type and name values in a merged synchronization archive. process_files_from_worker() in framework/wazuh/core/cluster/master.py does not adequately confine the resulting path to the declared cluster item directory. A cluster peer holding the shared Fernet key can use traversal in files_metadata.json or a merged-file header to write files such as /var/ossec/etc/ossec.conf. Replacing ossec.conf can configure root-executed commands and lead to code execution when Wazuh services reload. This issue is fixed in versions 4.14.6 and 5.0.0-beta3.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-48024
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 07:07 UTC · Revision 1
Source evidence
Wazuh: merged-file header path traversal in cluster sync allows arbitrary file write under WAZUH_PATH in Wazuh manager
core-osv · Original sourcePublished 19 Aug 2026, 16:14 UTC
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta3, cluster.unmerge_info() in framework/wazuh/core/cluster/cluster.py constructs paths from peer-controlled merge_type and name values in a merged synchronization archive. process_files_from_worker() in framework/wazuh/core/cluster/master.py does not adequately confine the resulting path to the declared cluster item directory. A cluster peer holding the shared Fernet key can use traversal in files_metadata.json or a merged-file header to write files such as /var/ossec/etc/ossec.conf. Replacing ossec.conf can configure root-executed commands and lead to code execution when Wazuh services reload. This issue is fixed in versions 4.14.6 and 5.0.0-beta3.
osv:CVE-2026-48024
Complete source record
{
"id": "4e0a2a552886ddaaf38e5070232d4b7032e7c7e255e43e9b6a2842a7cc06614d",
"url": "https://osv.dev/vulnerability/CVE-2026-48024",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Wazuh: merged-file header path traversal in cluster sync allows arbitrary file write under WAZUH_PATH in Wazuh manager",
"summary": "Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta3, cluster.unmerge_info() in framework/wazuh/core/cluster/cluster.py constructs paths from peer-controlled merge_type and name values in a merged synchronization archive. process_files_from_worker() in framework/wazuh/core/cluster/master.py does not adequately confine the resulting path to the declared cluster item directory. A cluster peer holding the shared Fernet key can use traversal in files_metadata.json or a merged-file header to write files such as /var/ossec/etc/ossec.conf. Replacing ossec.conf can configure root-executed commands and lead to code execution when Wazuh services reload. This issue is fixed in versions 4.14.6 and 5.0.0-beta3.",
"evidence": "osv:CVE-2026-48024",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2026-48024",
"aliases": [
"CVE-2026-48024",
"GHSA-gh4h-fx78-q8xc"
],
"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": "8c2c62a6e9dcbcf2c792f7924e8cfdb26842820b"
},
{
"fixed": "44c2925b46bd058d2426bd44ed1b3e5d7b7b03b4"
},
{
"introduced": "cddd833300cb5af494ba7dab31192bae649eb184"
},
{
"fixed": "88fc89fdfb1bf37b9d826e9c281a3d22655733de"
},
{
"fixed": "da844a6fdafd7388d11114841482596d1efdf5b3"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.0.0"
},
{
"fixed": "4.14.6"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:wazuh:wazuh:5.0.0:beta1:*:*:*:*:*:*",
"range": [
{
"introduced": "5.0.0-beta1"
},
{
"last_affected": "5.0.0-beta1"
}
],
"source": "CPE_STRING"
},
{
"cpe": "cpe:2.3:a:wazuh:wazuh:5.0.0:beta2:*:*:*:*:*:*",
"range": [
{
"introduced": "5.0.0-beta2"
},
{
"last_affected": "5.0.0-beta2"
}
],
"source": "CPE_STRING"
},
{
"range": [
{
"fixed": "88fc89fdfb1bf37b9d826e9c281a3d22655733de"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "44c2925b46bd058d2426bd44ed1b3e5d7b7b03b4"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v4.14.6"
},
{
"range": [
{
"fixed": "da844a6fdafd7388d11114841482596d1efdf5b3"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v5.0.0-beta3"
}
]
}
}
],
"versions": [
"5.0.0-beta1",
"5.0.0-beta2",
"v5.0.0-beta2",
"v5.0.0-beta1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-48024.json"
}
}
],
"modified": "2026-10-28T02:30:26.995595371Z",
"provider": "osv",
"references": [
"https://github.com/wazuh/wazuh/releases/tag/v4.14.6",
"https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta3",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48024.json",
"https://github.com/wazuh/wazuh/security/advisories/GHSA-gh4h-fx78-q8xc",
"https://nvd.nist.gov/vuln/detail/CVE-2026-48024",
"https://github.com/wazuh/wazuh/commit/88fc89fdfb1bf37b9d826e9c281a3d22655733de",
"https://github.com/wazuh/wazuh/pull/36204"
],
"provider_metadata": {
"cwe_ids": [
"CWE-22"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48024.json"
}
},
"related_cves": [
{
"value": "CVE-2026-48024",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 493229,
"published_at": "2026-08-19T16:14:20.847+00:00"
}