CVE-2026-28480
Authorization Bypass in OpenClaw Telegram Allowlist via Username Spoofing
Publication date: 2026-03-05
Last updated on: 2026-03-17
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.14 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-290 | This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions prior to 2026.2.14 and involves an authorization bypass. The issue arises because the Telegram allowlist matching process accepts mutable usernames instead of immutable numeric sender IDs. As a result, attackers can spoof their identity by obtaining recycled usernames, allowing them to bypass allowlist restrictions and interact with bots as unauthorized senders.
How can this vulnerability impact me? :
The vulnerability can allow attackers to impersonate authorized users by exploiting recycled usernames. This means unauthorized individuals could bypass security controls and interact with bots as if they were legitimate senders, potentially leading to unauthorized access, manipulation of bot interactions, or other malicious activities.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know