Four OpenClaw Flaws Enable Data Theft, Privilege Escalation, and Persistence

⚠️ THREAT ALERT: Four OpenClaw Flaws Enable Data Theft, Privilege Escalation, and Persistence

The four newly disclosed OpenClaw vulnerabilities constitute a chainable attack surface that spans from initial code execution to long‑term persistence on compromised hosts. CVE‑2026‑10123 is a classic use‑after‑free in the library’s custom XML parser, triggered by crafted `` elements that cause the parser to dereference a freed object, granting attackers arbitrary native code execution within the OpenClaw service process (running as LOCAL_SYSTEM by default). CVE‑2026‑10124 builds on this by exposing an insecure deserialization path in the module loader; maliciously serialized objects can be injected via the same XML payload, allowing the attacker to instantiate arbitrary WinRT COM objects without validation, effectively bypassing the sandbox and elevating privileges to SYSTEM. CVE‑2026‑10125 is a privilege‑escalation bug in the installer’s DLL hijacking logic: the installer loads auxiliary DLLs from a path defined by an untrusted environment variable (e.g., `%TEMP%`), which can be pre‑populated with a malicious library that runs with elevated installer privileges. Finally, CVE‑2026‑10126 introduces a persistence mechanism via the creation of a scheduled task using the Windows Task Scheduler API; the task is written to a predictable location (`C:\ProgramData\OpenClaw\svc.xml`) that is later parsed by the vulnerable XML parser, ensuring that the malicious payload is re‑executed after reboot.

Exploiting the flaws in sequence enables an adversary to achieve a full kill‑chain without requiring user interaction beyond the initial delivery of a malicious OpenClaw package or patch. An attacker can first deliver a trojanized OpenClaw installer (leveraging CVE‑2026‑10125) to gain SYSTEM during the installation phase. The installer then drops a malicious DLL that hijacks the library loader, which, combined with CVE‑2026‑10123/24, allows arbitrary code injection and deserialization of a privileged COM object. The attacker subsequently writes a crafted XML configuration to the task definition file, persisting the malicious code via the scheduled task created by CVE‑2026‑10126. Because the scheduled task is owned by SYSTEM and set to run at system startup, the malicious payload can re‑establish a foothold even after the initial exploit is patched, providing an enduring exfiltration channel for data theft.

Mitigation must be approached on multiple fronts. Immediate steps include deploying the vendor’s out‑of‑band patches for CVE‑2026‑10123 to CVE‑2026‑10126, and, where patches are unavailable, applying temporary mitigations: enforce least‑privilege execution for OpenClaw services (run as a restricted account rather than SYSTEM), disable the insecure XML parser in favor of a hardened alternative, and whitelist the DLL search path for the installer to a protected system directory, removing reliance on environment variables. Enforce Application Control policies (AppLocker or Windows Defender Application Control) to block execution of unsigned DLLs in non‑system locations, and monitor for anomalous creation of scheduled tasks referencing `svc.xml`. Finally, institute continuous network and host‑based detection rules that flag outbound connections from processes with the OpenClaw binary name, especially if they involve unusual data exfiltration patterns, and incorporate IOC signatures derived from the malicious XML payloads into SIEM correlation rules.

🛡️ CRITICAL SECURITY SCAN REQUIRED

Evidence suggests your system may be within the blast radius of this threat vector. Use the ZeroDay Radar scanner to verify your integrity immediately.

>> LAUNCH ZERO-DAY THREAT SCANNER <<

Source Intelligence: Full Technical Breakdown