
Cloud Vulnerability DB
A community-led vulnerabilities database
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.
openclaw (npm)<= 2026.3.122026.3.13The 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.
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).
7e49e98f79073b11134beac27fdff547ba5a4a02
Thanks @space08 for reporting.Source: NVD
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."