OpenClaw Telegram webhook request bodies were read before secret validation, enabling unauthenticated resource exhaustion
Summary
openclaw versions <= 2026.3.12 read and buffered Telegram webhook request bodies before validating x-telegram-bot-api-secret-token. This let unauthenticated callers force up to the configured webhook body limit of pre-auth body I/O and JSON parse work per request.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.3.12 - Fixed version:
2026.3.13
Details
The vulnerable path was the standalone Telegram webhook listener in src/telegram/webhook.ts. In affected releases, the request handler accepted POST requests, called readJsonBodyWithLimit(...), and only then checked the Telegram secret header. Because the secret validation happened after body reading, an unauthenticated caller could make the server spend memory, socket time, and JSON parse work on requests that should have been rejected before any body processing.
This issue is in scope under OpenClaw's trust model because the Telegram webhook endpoint accepts untrusted network traffic and the secret header is the authentication boundary for that ingress path.
Fix
openclaw@2026.3.13 validates the Telegram webhook secret before any body I/O. Current code reads the header, rejects invalid requests immediately with 401, and only calls readJsonBodyWithLimit(...) after hasValidTelegramWebhookSecret(...) succeeds.
Regression coverage exists in src/telegram/webhook.test.ts (rejects unauthenticated requests before reading the request body).
Fix Commit(s)
7e49e98f79073b11134beac27fdff547ba5a4a02
Thanks @space08 for reporting.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | openclaw | < 2026.3.13 | 2026.3.13 |
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-jq3f-vjww-8rq7
- https://nvd.nist.gov/vuln/detail/CVE-2026-32980
- https://github.com/openclaw/openclaw/commit/7e49e98f79073b11134beac27fdff547ba5a4a02
- https://github.com/openclaw/openclaw
- https://www.vulncheck.com/advisories/openclaw-resource-exhaustion-via-unauthenticated-telegram-webhook-request
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Weakness (CWE)
CWE-400, CWE-770- Platform
- npm
- Package
openclaw- Disclosed
- 16.03.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-jq3f-vjww-8rq7 - CC BY 4.0
Vulnerability history: openclaw
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 589
- First → latest
- 02.2026 10.2026
- Without a fix
- 9
- Exploited in attacks
- 0
Severity breakdown
- Critical 20
- High 215
- Medium 300
- Low 54
Disclosures per year
- 2026: 589
-
OpenClaw Telegram webhook request bodies were read before secret validation, enabling unauthenticated resource exhaustion this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.