CVE-2026-28448

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 allowFrom was configured, the code returned allowed: true for members but did not return allowed: false for non-members, so execution fell through.
• If allowedRoles was unset or empty, the function returned allowed: true by default, even when allowFrom was configured.

Proof of Concept (PoC)

1. Install and enable the Twitch plugin.
2. Configure an allowFrom list, but do not set allowedRoles (or set it to an empty list).
3. From a different Twitch account whose user ID is NOT in allowFrom, send a message that mentions the bot (for example @<botname> hello).
4. Observe the message is processed and can trigger agent dispatch/replies despite not being allowlisted.

Fix Commit(s)

• 8c7901c984866a776eb59662dc9d8b028de4f0d0

Workaround

Upgrade to openclaw >= 2026.2.1.

Thanks @MegaManSec (https://joshua.hu) of AISLE Research Team for reporting.

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.

CVE-2026-28448 has a CVSS score of 7.3 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-28448? CVE-2026-28448 is a high-severity security vulnerability in openclaw (npm), affecting versions >= 2026.1.29, < 2026.2.1. It is fixed in 2026.2.1.
2. How severe is CVE-2026-28448? CVE-2026-28448 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-28448? openclaw (npm) versions >= 2026.1.29, < 2026.2.1 is affected.
4. Is there a fix for CVE-2026-28448? Yes. CVE-2026-28448 is fixed in 2026.2.1. Upgrade to this version or later.
5. Is CVE-2026-28448 exploitable, and should I be worried? Whether CVE-2026-28448 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-28448 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-28448? Upgrade openclaw to 2026.2.1 or later.