GHSA-33rq-m5x2-fvgf is a high-severity (CVSS 7.3) CWE-285 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
OpenClaw Twitch allowFrom is not enforced in optional plugin, unauthorized chat users can trigger agent pipeline
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-33rq-m5x2-fvgf.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-33rq-m5x2-fvgf plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
openclawnpmDescription
Summary
In the optional Twitch channel plugin (extensions/twitch), allowFrom is documented as a hard allowlist of Twitch user IDs, but it was not enforced as a hard gate. If allowedRoles is unset or empty, the access control path defaulted to allow, so any Twitch user who could mention the bot could reach the agent dispatch pipeline.
Scope note: This only affects deployments that installed and enabled the Twitch plugin. Core OpenClaw installs that do not install/enable the Twitch plugin are not impacted.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
>= 2026.1.29, < 2026.2.1 - Fixed:
>= 2026.2.1
Details
Affected component: Twitch plugin access control (extensions/twitch/src/access-control.ts).
Problematic logic in checkTwitchAccessControl():
- When
allowFromwas configured, the code returnedallowed: truefor members but did not returnallowed: falsefor non-members, so execution fell through. - If
allowedRoleswas unset or empty, the function returnedallowed: trueby default, even whenallowFromwas configured.
Proof of Concept (PoC)
- Install and enable the Twitch plugin.
- Configure an
allowFromlist, but do not setallowedRoles(or set it to an empty list). - From a different Twitch account whose user ID is NOT in
allowFrom, send a message that mentions the bot (for example@<botname> hello). - Observe the message is processed and can trigger agent dispatch/replies despite not being allowlisted.
Impact
Authorization bypass for operators who relied on allowFrom to restrict who can invoke the bot in Twitch chat. Depending on configuration (tools, routing, model costs), this could lead to unintended actions/responses and resource or cost exhaustion.
Fix Commit(s)
8c7901c984866a776eb59662dc9d8b028de4f0d0
Workaround
Upgrade to openclaw >= 2026.2.1.
Thanks @MegaManSec (https://joshua.hu) of AISLE Research Team for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | ≥ 2026.1.29&&< 2026.2.1 | 2026.2.1npm install openclaw@2026.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33rq-m5x2-fvgf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-33rq-m5x2-fvgf can be triaged on real exposure rather than presence alone.
Tailored to GHSA-33rq-m5x2-fvgf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-33rq-m5x2-fvgf in your dependencies?
O3 Security finds GHSA-33rq-m5x2-fvgf across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.