These examples are historical advisories or reported campaigns, not allegations that every current installation is vulnerable. Named upstream fixes matter. The Clawsolator column describes additional operator defenses that may reduce blast radius—not a guarantee of prevention.
CASE STUDY 01
Historical OpenClaw node approval bypass
Cause: A gateway-to-node approval validation flaw allowed an authenticated actor to cause node-host commands to execute on affected versions.
What reduces exposure: Upstream patched in OpenClaw 2026.2.14. Independent host execution gates help contain some consequences but are not a replacement for the patch.
Original evidence: GHSA-gv46-4xfq-jv58 – historical node approval bypass (fixed) ↗
CASE STUDY 02
Historical device-pairing scope escalation
Cause: Pairing authority was able to approve a device for scopes beyond those held by the approver.
What reduces exposure: OpenClaw shipped a fix. Re-check privilege grant boundaries and isolate privileged host requests.
Original evidence: GHSA-hf68-49fm-59cq – historical pairing scope escalation (fixed) ↗
CASE STUDY 03
Historical HTTP tool / ACP escalation
Cause: Authenticated tool invocation and insufficient approval handling increased impact in exposed or misconfigured gateways.
What reduces exposure: Upgrade affected releases and restrict tools, roles and gateway exposure.
Original evidence: GHSA-943q-mwmv-hhvh – historical tool escalation (fixed) ↗
CASE STUDY 04
ClawHavoc third-party skill campaign
Cause: Researchers reported malicious skills masquerading as useful integrations, sometimes asking operators to paste malicious commands.
What reduces exposure: Use upstream skill scanning, explicit installation reviews, least-privilege filesystem/egress, and operator education.
Original evidence: ClawHavoc campaign summary, referencing Koi Security research ↗