CVE-2026-32980: 
OpenClaw (formerly Moltbot or Clawdbot) vulnerability analysis and mitigation

CVE-2026-32980 is a resource exhaustion vulnerability in OpenClaw, a Node.js-based Telegram bot framework, caused by reading and buffering webhook request bodies before validating the x-telegram-bot-api-secret-token authentication header. All versions up to and including 2026.3.12 are affected; the issue was fixed in version 2026.3.13. The vulnerability was published on March 29, 2026, and assigned by VulnCheck. It carries a CVSS v3.1 base score of 7.5 (High) and a CVSS v4.0 base score of 8.7 (High) (GitHub Advisory, Feedly).

The root cause is classified as CWE-770 (Allocation of Resources Without Limits or Throttling) — specifically, the Telegram webhook handler in src/telegram/webhook.ts called readJsonBodyWithLimit(...) to fully read and buffer the POST request body before checking the x-telegram-bot-api-secret-token header. This means any unauthenticated network attacker can send POST requests to the webhook endpoint, forcing the server to consume memory (up to the configured body limit, approximately 1 MB per request), hold open socket connections, and perform JSON parsing work — all before any authentication check occurs. No special privileges or user interaction are required; the attack vector is purely network-based (GitHub Advisory, Fix Commit).

Successful exploitation results in a denial-of-service (DoS) condition by exhausting server memory, socket connections, and CPU time through JSON parsing on unauthenticated requests. There is no impact on confidentiality or data integrity — the vulnerability is purely an availability issue. Under sustained attack, legitimate Telegram bot traffic would be unable to be processed, effectively taking the bot offline (GitHub Advisory, Feedly).

No public proof-of-concept exploit code has been identified, and there is no evidence of in-the-wild exploitation at this time. The EPSS score is approximately 0.064%, reflecting low current exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Despite the absence of a PoC, the attack is trivially executable — any attacker capable of sending HTTP POST requests to the webhook endpoint can trigger resource exhaustion without authentication (Feedly, GitHub Advisory).

1. Reconnaissance: Identify publicly exposed OpenClaw webhook endpoints by scanning for Node.js HTTP servers or searching for known OpenClaw deployment patterns. The webhook path is typically configured by the deployer.
2. Craft malicious POST request: Prepare an HTTP POST request targeting the Telegram webhook endpoint with a large Content-Length header (up to ~1 MB) and either no x-telegram-bot-api-secret-token header or an invalid one.
3. Send repeated requests: Flood the server with concurrent POST requests containing large declared body sizes. Each request forces the server to read and buffer the full body and attempt JSON parsing before rejecting the request.
4. Resource exhaustion: The cumulative effect of many concurrent requests exhausts server memory, socket file descriptors, and CPU cycles allocated to JSON parsing, causing the service to become unresponsive to legitimate Telegram webhook traffic (GitHub Advisory, Fix Commit).

• Network: High volume of HTTP POST requests to the Telegram webhook endpoint from diverse or unexpected source IPs; requests with large Content-Length values but missing or invalid x-telegram-bot-api-secret-token headers.
• Logs: Server access logs showing repeated POST requests to the webhook path returning 401 responses after a delay (indicating body was read before rejection in unpatched versions); abnormally high request rates to the webhook endpoint.
• Process/System: Elevated Node.js process memory consumption; increased CPU usage associated with JSON parsing activity; socket exhaustion or connection queue saturation on the webhook listener port.
• Application: Degraded or failed processing of legitimate Telegram updates; increased latency or timeouts on the webhook handler (GitHub Advisory).

Upgrade OpenClaw to version 2026.3.13 or later, which validates the x-telegram-bot-api-secret-token header before reading any request body, immediately rejecting unauthorized requests with a 401 response and closing the connection. No configuration-based workaround is available for unpatched versions; upgrading is the only effective remediation. As an interim network-level measure, operators may consider rate-limiting POST requests to the webhook endpoint at the reverse proxy or firewall layer to reduce the impact of flooding attacks (GitHub Advisory, Fix Commit).

The vulnerability was reported by researcher @space08 and acknowledged by the OpenClaw maintainers, who issued a fix promptly. Brief mentions appeared on Mastodon and Bluesky CVE tracking accounts shortly after disclosure. Security aggregators including RedPacket Security, InfinitSec, and Yazoul published CVE alert summaries. No significant broader media coverage or notable researcher commentary beyond routine CVE tracking has been identified (Feedly).