CVE-2026-61800PoC(wazuh / wazuh)

LOWCVSS 9.1 · CRITICAL

Exploit discussion active in current signal (1 latest mentions)

Immediate actions

  • Hunt for exploitation attempts and persistence artifacts
  • Increase monitoring for publicly documented tradecraft
  • Track advisory updates for patch or workaround availability

Recommended action window: High priority (within 72h)

NVD 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.

1.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-22

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • wazuh

Threat summary

  • Public PoC is present in monitored signal
  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • PoC mentioned or linked in 1 signal
  • Technical details provided in 2 signals
  • Disclosure: 1 classified signal
  • Peaked 1d ago at 1 mentions (2026-08-28); latest day: 1
  • 2 total mentions across 2 days

Affected systems

Vendors
Products
wazuh

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-08-28: 1Mentions · 2026-08-30: 1PoC Mentioned / Linked · 2026-08-28: 1Technical Details · 2026-08-28: 1Technical Details · 2026-08-30: 108-2808-30
Signal classification2 categories
PoC
150.0%
Disclosure
150.0%
Referenced assets2 URLs
Classification over time
DateTotalLabels
2026-08-281
PoC1
2026-08-301
Disclosure1
Full discourse2 posts
  • Cybersecurity News DE@cybsecuritynews
    Disclosure

    #schwachstellen Kritische Wazuh-Lücke erlaubt Root-Codeausführung auf Worker-Nodes #cve202630893 #cve202661800 #wazuh https://cybersecurity-news.de/cve-2026-61800-wazuh-root-codeausfuehrung-worker-nodes

    Post summary

    The tweet announces a critical root code execution flaw in Wazuh worker nodes, referencing CVE‑2026‑30893 and CVE‑2026‑61800.

    0000047
    10 followersView on X
  • Hephaestvs@Vulcanux_
    PoC

    csirt_it: ‼️ #PoC #Wazuh: Disponibile Proof of Concept per CVE-2026-61800 e CVE-2026-54083 Rischio: 🔴 Tipologia: 🔸 Remote Code Execution 🔸 Information Disclosure 🔸 Security Restrictions Bypass 🔗 https://www.acn.gov.it/portale/w/wazuh-disponibili-poc-per-le-cve-2026-54083-e-cve-2026-61800 ⚠️ Importante mantenere ag… https://t.co/ygyUtZIi1d

    Post summary

    The post announces that PoC code is publicly available for CVE‑2026‑61800 and CVE‑2026‑54083, detailing the vulnerability types such as RCE and information disclosure.

    0000058
    633 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appwazuhwazuh---

Explore more