How severe is CVE-2026-28448?

No CVSS score has been assigned to CVE-2026-28448 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-28448?

CVE-2026-28448 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix CVE-2026-28448?

Update openclaw to 2026.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28448 is resolved across your whole dependency graph.

How do I detect CVE-2026-28448 in my npm dependencies?

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.

How do I mitigate CVE-2026-28448 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-28448 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-28448 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-28448?

CVE-2026-28448 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-28448?

CVE-2026-28448 is classified as CWE-285 (CWE-285). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-28448 published, and has it been updated?

CVE-2026-28448 was published on March 5, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-28448 — openclaw

Fix: openclaw/openclaw@8c7901c

CVE-2026-28448 is a CWE-285 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw 2026.1.29 < 2026.2.1 - Authorization Bypass in Twitch Plugin allowFrom Access Control

Also known asGHSA-33rq-m5x2-fvgf

Published

Mar 5, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2026-28448.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

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.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.9Mdownloads / week

Description

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 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)

Install and enable the Twitch plugin.
Configure an allowFrom list, but do not set allowedRoles (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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.1.29&&< 2026.2.1	2026.2.1`npm install openclaw@2026.2.1`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

≥ 2026.1.29 && < 2026.2.1

range

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2026-28448 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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:

O3 Security · Impact-Aware SCA

Is CVE-2026-28448 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works