CVE-2026-28480: Openclaw cli · OpenClaw Telegram allowlist authorization accepted mutable usernames
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 5.9 Medium : upgrade to 2026.2.14 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.14
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.2.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and should be applied to upgrade to versions >=2026.2.14 where the fix is implemented. The fix rejects username-based allowlist entries and requires numeric Telegram sender IDs. Operators should run 'openclaw doctor --fix' to convert legacy username allowlist entries to numeric IDs, which requires a Telegram bot token. The vendor added a security audit warning to flag legacy configurations. No further action is required once patched.
Description
OpenClaw CLI versions before 2026.2.14 allowed Telegram allowlist authorization based on mutable usernames instead of immutable numeric sender IDs. This flaw could let unauthorized users gain access if a username is recycled or changed hands. The vulnerability has been fixed by requiring numeric Telegram sender IDs only and rejecting username-based allowlist entries. A security audit warning and a fix command are provided to help migrate legacy configurations.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-mj5r-hh7j-4gxf (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-28480 (opens in a new tab)
- github.com/openclaw/openclaw/commit/9e147f00b48e63e7be6964e0e2a97f2980854128 (opens in a new tab)
- github.com/openclaw/openclaw/commit/e3b432e481a96b8fd41b91273818e514074e05c3 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- github.com/openclaw/openclaw/releases/tag/v2026.2.14 (opens in a new tab)
- vulncheck.com/advisories/openclaw-identity-spoofing-via-mutable-username-in-telegram-allowlist-authorization (opens in a new tab)