This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis β
Q1What is this vulnerability? (Essence + Consequences)
π¨ **Essence**: OpenClaw fails to validate Windows `cmd.exe` metacharacters properly. π **Consequences**: Attackers bypass command approval limits and execute unauthorized commands.β¦
π₯ **Affected**: Users of **OpenClaw** (OpenClaw open-source AI assistant). π **Versions**: All versions **prior to 2026.2.2**. π’ **Vendor**: OpenClaw.
Q4What can hackers do? (Privileges/Data)
π» **Privileges**: High. CVSS Score indicates **High** Confidentiality, Integrity, and Availability impact. π΅οΈ **Action**: Execute **unapproved commands** on the host.β¦
π **Threshold**: **Low**. π« **Auth**: No authentication required (PR:N). ποΈ **UI**: No user interaction needed (UI:N). π **Vector**: Network accessible (AV:N). β‘ **Complexity**: Low (AC:L).
Q6Is there a public Exp? (PoC/Wild Exploitation)
π« **Public Exp**: No public PoC or exploit code listed in the data. π **References**: Only vendor advisory and patch commit links available. π΅οΈ **Status**: Theoretical/Unpatched exploitation risk exists.
Q7How to self-check? (Features/Scanning)
π **Check**: Scan for OpenClaw installations. π¦ **Version**: Verify if version < **2026.2.2**. π οΈ **Tool**: Use VulnCheck or GitHub Security Advisories to detect presence.β¦
β **Fixed**: Yes. π¦ **Patch**: Update to **OpenClaw 2026.2.2** or later. π **Source**: Official patch commit available on GitHub (a7f4a53ce80c98ba1452eb90802d447fca9bf3d6).
Q9What if no patch? (Workaround)
π§ **Workaround**: If patching is delayed, restrict network access to OpenClaw services. π **Mitigation**: Implement strict WAF rules to block `cmd.exe` metacharacter injection attempts.β¦