OpenClaw Telegram Allowlist Vulnerability: Mutable Usernames Risk

openclaw Updated 18 Feb 2026

Summary

18/02/2026

Disclosed on

MODERATE

Severity

Yes i

Fix available

Moderate

Severity

5.9

CVSS Score

GHSA-mj5r-hh7j-4gxf: OpenClaw Telegram allowlist authorization accepted mutable usernames. Affects openclaw versions < 2026.2.14. Fixed in 2026.2.14. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

OpenClaw is an npm package designed for integrating Telegram bots with various functionalities, including user management through allowlists. It allows operators to control access to their bots based on user identities. However, the package has a vulnerability that arises from its reliance on mutable usernames, which can be recycled or changed, leading to potential unauthorized access.

Vulnerability Detail

The vulnerability stems from the Telegram allowlist authorization mechanism, which matches on mutable usernames (e.g., @username) instead of immutable numeric sender IDs. This can lead to identity rebinding or spoofing risks, where an unauthorized sender could gain access to the bot if a username changes hands. Operators relying on allowlists for strict identity control may inadvertently grant access to malicious actors.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.2.14

This is the first release that contains the fix.

npm install openclaw@2026.2.14

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, avoid using @username in your allowlist configurations. Instead, ensure that only numeric Telegram sender IDs are included in the allowlist to prevent unauthorized access.

Conclusion

The OpenClaw Telegram allowlist vulnerability poses a significant risk due to its reliance on mutable usernames for authorization. Operators are encouraged to update their packages to the latest versions and implement best practices to secure their bots against unauthorized access.

See every vulnerability recorded for openclaw →