openclaw
Affected
- introduced
0, fixed2026.2.14(semver)
Fixed versions
2026.2.14
Fix
- Fixed version
2026.2.14npm install [email protected]
Advisory
Also known as: CVE-2026-28480
OpenClaw Telegram allowlist authorization accepted mutable usernames
Summary
Telegram allowlist authorization could match on @username (mutable/recyclable) instead of immutable numeric sender IDs.
Impact
Operators who treat Telegram allowlists as strict identity controls could unintentionally grant access if a username changes hands (identity rebinding/spoof risk). This can allow an unauthorized sender to interact with the bot in allowlist mode.
Affected Packages / Versions
openclaw: <= 2026.2.13clawdbot: <= 2026.1.24-3Fix
Telegram allowlist authorization now requires numeric Telegram sender IDs only. @username allowlist principals are rejected.
A security audit warning was added to flag legacy configs that still contain non-numeric Telegram allowlist entries.
openclaw doctor --fix now attempts to resolve @username allowFrom entries to numeric IDs (best-effort; requires a Telegram bot token).
Fix Commit(s)
Thanks @vincentkoc for reporting.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.2.14 (semver)2026.2.14
2026.2.14npm install [email protected]0, last affected 2026.1.24-3 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0