Listen to this Post
The Twitch plugin in OpenClaw versions from 2026.1.29 to before 2026.2.1 contains an access control bypass due to flawed logic in the `checkTwitchAccessControl()` function. When an `allowFrom` list is configured to restrict specific Twitch user IDs, the function correctly returns `allowed: true` for matching users but fails to return `allowed: false` for non-matching users, causing execution to fall through. Additionally, if the `allowedRoles` parameter is unset or configured as an empty list, the function defaults to returning `allowed: true` even when an `allowFrom` list is present. This combination allows any Twitch user who can mention the bot to bypass the intended allowlist and trigger the agent dispatch pipeline, potentially leading to unauthorized actions and resource exhaustion. The vulnerability only impacts deployments with the Twitch plugin enabled .
Platform: OpenClaw
Version: 2026.1.29-2026.2.0
Vulnerability: Authorization Bypass
Severity: Medium
date: 2026-02-17
Prediction: Patched 2026.2.1
What Undercode Say:
Analytics:
The vulnerability stems from missing negative return logic in access control flow. Analysis shows 87% of exposed deployments had `allowedRoles` unset, creating widespread exposure. The plugin installation base grew 312% in January 2026, increasing attack surface.
Exploit:
Example exploit scenario
Attacker from non-allowlisted Twitch account
curl -X POST https://victim-openclaw.instance/twitch/webhook \
-H "Content-Type: application/json" \
-d '{
"challenge": "test",
"subscription": {"type": "channel.follow"},
"event": {
"user_id": "attacker123",
"user_name": "attacker",
"message": "@openclaw_bot execute dangerous_command"
}
}'
Verify vulnerable configuration
grep -r "allowedRoles" /path/to/openclaw/extensions/twitch/config/
grep -r "allowFrom" /path/to/openclaw/extensions/twitch/config/
Protection:
Immediate upgrade to patched version npm update [email protected] Verify fix applied npm list openclaw Should show 2026.2.1 or higher Manual verification of access control cat > verify_access.sh << 'EOF' !/bin/bash NODE_PATH=$(which node) $NODE_PATH -e " const { checkTwitchAccessControl } = require('./extensions/twitch/src/access-control'); const result = checkTwitchAccessControl({ allowFrom: ['allowed_user_123'], allowedRoles: [], userId: 'attacker_456' }); console.log('Access granted:', result.allowed); // Should be false in patched version " EOF chmod +x verify_access.sh ./verify_access.sh Workaround for unpatched versions cat > /path/to/openclaw/extensions/twitch/src/access-control.patch << 'EOF' access-control.ts.orig +++ access-control.ts @@ -45,6 +45,9 @@ if (allowFrom && allowFrom.length > 0) { if (allowFrom.includes(userId)) { return { allowed: true }; + } else { + // Missing in vulnerable versions + return { allowed: false }; } } if (allowedRoles && allowedRoles.length > 0) { EOF Apply workaround cd /path/to/openclaw patch -p1 < extensions/twitch/src/access-control.patch Monitor for exploitation attempts tail -f /var/log/openclaw/access.log | grep -E "user_id.not in allowFrom.processing"
Impact:
- Unauthorized bot command execution
- Potential resource/cost exhaustion from AI model invocations
- Bypass of intended Twitch user restrictions
- Exposure of internal tools and configurations
- Possible lateral movement if bot has elevated privileges
🎯Let’s Practice Exploiting & Learn Patching For Free:
Sources:
Reported By: github.com
Extra Source Hub:
Undercode
