[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-CVE-2026-61800":6},{"stargazers_count":4,"fetched_at":5},7,"2026-08-27T23:51:06.732Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":40,"aliases":41,"duplicate_of":9,"upstream":42,"downstream":43,"duplicates":44,"related":45,"reserved_at":9,"published_at":46,"modified_at":46,"state":47,"summary":48,"references_raw":55,"kevs":67,"epss":9,"epss_history":68,"metrics":69,"affected":77},"CVE-2026-61800","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.",null,[11],{"_key":12,"id":12,"name":13,"description":14,"type":15,"status":16,"abstraction":17,"likelihood_of_exploit":18,"capec":19},"CWE-22","Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')","The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.","weakness","Stable","Base","High",[20,24,28,32,36],{"id":21,"name":22,"techniques":23},"CAPEC-126","Path Traversal",[],{"id":25,"name":26,"techniques":27},"CAPEC-64","Using Slashes and URL Encoding Combined to Bypass Validation Logic",[],{"id":29,"name":30,"techniques":31},"CAPEC-76","Manipulating Web Input to File System Calls",[],{"id":33,"name":34,"techniques":35},"CAPEC-78","Using Escaped Slashes in Alternate Encoding",[],{"id":37,"name":38,"techniques":39},"CAPEC-79","Using Slashes in Alternate Encoding",[],[],[],[],[],[],[],"2026-08-27T23:26:28.110Z","Received",{"cisa_kev":49,"cisa_ransomware":49,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":50,"severity_score":51,"severity_version":52,"severity_source":53,"severity_vector":54,"severity_status":47},false,"critical",9.1,"v3.1","cve.org","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",[56,62],{"url":57,"sources":58,"tags":60},"https://github.com/wazuh/wazuh/security/advisories/GHSA-3jff-488g-335f",[53,59],"nvd",[61],"X Refsource CONFIRM",{"url":63,"sources":64,"tags":65},"https://github.com/wazuh/wazuh/commit/f7f7c4d2d9e683c5d42e997fe7028a3fb2578853",[53,59],[66],"X Refsource MISC",[],[],[70,75],{"source":53,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":71,"cvss_v4_0":9},{"baseScore":51,"baseSeverity":72,"vectorString":54,"impactScore":73,"exploitabilityScore":74},"CRITICAL",10,5.9,{"source":59,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":76,"cvss_v4_0":9},{"baseScore":51,"baseSeverity":72,"vectorString":54,"impactScore":73,"exploitabilityScore":74},[78],{"ecosystem":9,"name":79,"vendor":79,"product":79,"cpe_part":80,"purl_type":9,"purl_namespace":9,"purl_name":9,"source":9,"versions":81},"wazuh","a",[82],{"version":83,"is_range":84,"range_type":53,"version_start":85,"version_start_type":86,"version_end":87,"version_end_type":88,"fixed_in":9},">= 4.4.0, \u003C 4.14.7",true,"4.4.0","including","4.14.7","excluding"]