Vulnerabilities in pkg:npm/clawdbot
PACKAGECVE-2026-28480 is a MODERATE (CVSS 5.9) openclaw telegram allowlist authorization accepted vulnerability (CWE-284: Improper Access Control) affecting Openclaw libraries in the npm ecosystem. The issue involves openclaw telegram allowlist authorization accepted mutable usernames. Remediation is available by upgrading affected packages to version 2026.2.14.
pkg:npm/clawdbot
Vulnerability advisories affecting package pkg:npm/clawdbot. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-mj5r-hh7j-4gxf | CVE-2026-28480 | MODERATE | OpenClaw Telegram allowlist authorization accepted mutable usernames |
| GHSA-rq6g-px6m-c248 | CVE-2026-28469 | HIGH | OpenClaw Google Chat shared-path webhook target ambiguity allowed cross-account policy-context misrouting |
| GHSA-w2cg-vxx6-5xjg | CVE-2026-29612 | MODERATE | OpenClaw: denial of service through large base64 media files allocating large buffers before limit checks |
| GHSA-h89v-j3x9-8wqj | CVE-2026-28452 | MODERATE | OpenClaw affected by denial of service through unguarded archive extraction allowing high expansion/resource abuse (ZIP/TAR) |
| GHSA-q447-rj3r-2cgh | CVE-2026-28478 | HIGH | OpenClaw affected by denial of service via unbounded webhook request body buffering |
| GHSA-3fqr-4cg8-h96q | CVE-2026-26317 | HIGH | OpenClaw affected by cross-site request forgery (CSRF) through loopback browser mutation endpoints |
| GHSA-g34w-4xqq-h79m | CVE-2026-26328 | MODERATE | OpenClaw iMessage group allowlist authorization inherited DM pairing-store identities |
| GHSA-chm2-m3w2-wcxm | - | LOW | OpenClaw Google Chat spoofing access with allowlist authorized mutable email principal despite sender-ID mismatch |
| GHSA-q284-4pvr-m585 | CVE-2026-25157 | HIGH | OpenClaw/Clawdbot has OS Command Injection via Project Root Path in sshNodeCommand |
| GHSA-mc68-q9jw-2h3v | CVE-2026-24763 | HIGH | OpenClaw/Clawdbot Docker Execution has Authenticated Command Injection via PATH Environment Variable |
| GHSA-g8p2-7wf7-98mq | CVE-2026-25253 | HIGH | OpenClaw/Clawdbot has 1-Click RCE via Authentication Token Exfiltration From gatewayUrl |
| GHSA-r2c6-8jc8-g32w | - | HIGH | Duplicate Advisory: 1-Click RCE via Authentication Token Exfiltration From gatewayUrl |
CVE-2026-28480 at a Glance
Security Impact
CVSS: 5.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N).
How to Fix CVE-2026-28480
To remediate this vulnerability, upgrade all affected Openclaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install openclaw@2026.2.14
npm install clawdbot@Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls openclaw
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-28480, inspect your project dependencies using npm:
npm ls openclaw
Analyze the terminal output to locate any version of Openclaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.2.14), your application is affected.
Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Openclaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-28480 Affected Openclaw Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
openclaw
|
npm |
< 2026.2.14
|
2026.2.14
|
|
clawdbot
|
npm |
≤ 2026.1.24-3
|
|
References
Frequently Asked Questions
What is CVE-2026-28480?
Which Openclaw versions are affected?
What version fixes CVE-2026-28480?
Is openclaw affected?
Is clawdbot affected?
What is the CVSS score of CVE-2026-28480?
What CWE is associated with CVE-2026-28480?
How can I check npm dependencies for CVE-2026-28480?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-mj5r-hh7j-4gxf",
"modified" : "2026-03-06T01:03:30Z",
"published" : "2026-02-18T00:54:32Z",
"aliases" : [ "CVE-2026-28480" ],
"summary" : "OpenClaw Telegram allowlist authorization accepted mutable usernames",
"details" : "## Summary\nTelegram allowlist authorization could match on `@username` (mutable/recyclable) instead of immutable numeric sender IDs.\n\n## Impact\nOperators 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.\n\n## Affected Packages / Versions\n- npm `openclaw`: <= 2026.2.13\n- npm `clawdbot`: <= 2026.1.24-3\n\n## Fix\nTelegram allowlist authorization now requires numeric Telegram sender IDs only. `@username` allowlist principals are rejected.\n\nA security audit warning was added to flag legacy configs that still contain non-numeric Telegram allowlist entries.\n\n`openclaw doctor --fix` now attempts to resolve `@username` allowFrom entries to numeric IDs (best-effort; requires a Telegram bot token).\n\n## Fix Commit(s)\n- e3b432e481a96b8fd41b91273818e514074e05c3\n- 9e147f00b48e63e7be6964e0e2a97f2980854128\n\nThanks @vincentkoc for reporting.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "openclaw"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2026.2.14"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "clawdbot"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "2026.1.24-3"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-mj5r-hh7j-4gxf"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-28480"
}, {
"type" : "WEB",
"url" : "https://github.com/openclaw/openclaw/commit/9e147f00b48e63e7be6964e0e2a97f2980854128"
}, {
"type" : "WEB",
"url" : "https://github.com/openclaw/openclaw/commit/e3b432e481a96b8fd41b91273818e514074e05c3"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/openclaw/openclaw"
}, {
"type" : "WEB",
"url" : "https://github.com/openclaw/openclaw/releases/tag/v2026.2.14"
}, {
"type" : "WEB",
"url" : "https://www.vulncheck.com/advisories/openclaw-identity-spoofing-via-mutable-username-in-telegram-allowlist-authorization"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-284", "CWE-290" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-02-18T00:54:32Z",
"nvd_published_at" : "2026-03-05T22:16:22Z"
}
}