7.5

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-q447-rj3r-2cgh

GHSA-q447-rj3r-2cgh: OpenClaw affected by denial of service via unbounded webhook request body buffering

Summary

Multiple webhook handlers accepted and buffered request bodies without a strict unified byte/time limit. A remote unauthenticated attacker could send oversized payloads and cause memory pressure, degrading availability.

Details

Affected packages:

openclaw (npm): <2026.2.12
clawdbot (npm): <=2026.1.24-3

Root cause:

Webhook code paths buffered request payloads without consistent maxBytes + timeoutMs enforcement.
Some SDK-backed handlers parse request bodies internally and needed stream-level guards.

Attack shape:

Send very large JSON payloads or slow/incomplete uploads to webhook endpoints.
Observe elevated memory usage and request handler pressure.

Impact

Remote unauthenticated availability impact (DoS) via request body amplification/memory pressure.

Patch details (implemented)

Added shared bounded request-body helper in src/infra/http-body.ts.
Exported helper in src/plugin-sdk/index.ts for extension reuse.
Migrated webhook body readers to shared helper for:
- LINE
- Nextcloud Talk
- Google Chat
- Zalo
- BlueBubbles
- Nostr profile HTTP
- Voice-call
- Gateway hooks
Added stream guards for SDK handlers that parse request bodies internally:
- Slack
- Telegram
- Feishu
Added explicit Express JSON body limit handling for MS Teams webhook path.
Standardized failure responses:
- 413 Payload Too Large
- 408 Request Timeout

Tests

Added regression tests:
- src/infra/http-body.test.ts
- src/line/monitor.read-body.test.ts
- extensions/nextcloud-talk/src/monitor.read-body.test.ts
Focused webhook/security test suite passes for patched paths.

Remediation

Upgrade to the first release containing this patch.

Credits

Thanks @vincentkoc for reporting.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-q447-rj3r-2cgh

GHSA-q447-rj3r-2cgh:

7.5

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	< 2026.2.13	2026.2.13
clawdbot	npm	<= 2026.1.24-3

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the unbounded buffering of HTTP request bodies across multiple webhook handlers in the OpenClaw application. The advisory and the patch confirm that various components were accepting and processing request bodies without enforcing a strict size or time limit. An unauthenticated attacker could exploit this by sending very large or slow-streaming payloads to these webhook endpoints, causing excessive memory consumption on the server and leading to a denial of service (DoS).

The patch addresses this by introducing a centralized and reusable set of functions in src/infra/http-body.ts: readRequestBodyWithLimit, readJsonBodyWithLimit, and installRequestBodyLimitGuard. These helpers are designed to read request bodies while enforcing maxBytes and timeoutMs limits.

The analysis of the fixing commit (3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930) shows that numerous webhook handlers were refactored to use these new, secure helpers. The vulnerable functions are the ones that previously contained or called insecure code to read the request body. For example, many files had their own local, insecure readJsonBody or readBody implementation which was removed. In other cases, like for Slack, Telegram, and Feishu, the patch wraps the existing SDK-provided request handlers with installRequestBodyLimitGuard to enforce the limits at the stream level before the SDK can buffer the data. For MS Teams, the fix was to correctly configure the body limit in the Express.js JSON middleware.

The identified vulnerable_functions are the primary entry points for these webhooks, which were responsible for initiating the insecure reading of the request body before the patch was applied.

Vulnerable functions

handleBlueBubblesWebhookRequest

extensions/bluebubbles/src/monitor.ts

The `handleBlueBubblesWebhookRequest` function used an insecure `readJsonBody` function that buffered the entire request body in memory without a size limit, making it vulnerable to denial of service by sending a large payload.

monitorWebhook

extensions/feishu/src/monitor.ts

The `monitorWebhook` function registered a Feishu webhook handler directly to the HTTP server without any request body size enforcement. An attacker could send a large payload, causing the server to run out of memory.

handleGoogleChatWebhookRequest

extensions/googlechat/src/monitor.ts

The `handleGoogleChatWebhookRequest` function used an insecure `readJsonBody` function that buffered the entire request body in memory without a proper size limit, making it vulnerable to denial of service.

monitorMSTeamsProvider

extensions/msteams/src/monitor.ts

The `monitorMSTeamsProvider` function configured an Express.js application with `express.json()` without a `limit` option. This allowed an attacker to send an oversized JSON payload, leading to a denial of service.

createNextcloudTalkWebhookServer

extensions/nextcloud-talk/src/monitor.ts

The `createNextcloudTalkWebhookServer` function used an insecure `readBody` function that read the entire request body into memory without any size restrictions, making it susceptible to a denial-of-service attack.

handleNostrProfileHttpRequest

extensions/nostr/src/nostr-profile-http.ts

The `handleNostrProfileHttpRequest` function (which is the main handler in the file) called an insecure `readJsonBody` function that did not properly limit the request body size, leading to a potential denial of service.

VoiceCallWebhookServer.handleRequest

extensions/voice-call/src/webhook.ts

The `handleRequest` method of the `VoiceCallWebhookServer` class used an insecure `readBody` method that buffered the request body without a size limit, creating a denial-of-service vulnerability.

handleZaloWebhookRequest

extensions/zalo/src/monitor.ts

The `handleZaloWebhookRequest` function used an insecure `readJsonBody` function that did not properly enforce the `maxBytes` limit until after buffering potentially large chunks, leading to a denial-of-service vulnerability.

createHooksRequestHandler

src/gateway/server-http.ts

The `createHooksRequestHandler` function, which handles generic gateway hooks, used an insecure `readJsonBody` function (from `src/gateway/hooks.ts`) that buffered the request body without a proper size limit.

monitorLineProvider

src/line/monitor.ts

The main request handler within `monitorLineProvider` used an insecure `readRequestBody` function that read the entire request body into memory without any size limit, making it vulnerable to denial of service.

monitorSlackProvider

src/slack/monitor/provider.ts

The `monitorSlackProvider` function created a `slackHttpHandler` that processed Slack webhook requests. This handler did not have a request body size limit, allowing an attacker to cause a denial of service by sending a large payload.

startTelegramWebhook

src/telegram/webhook.ts

The `startTelegramWebhook` function set up an HTTP server to handle Telegram webhooks. The handler was not protected by any request body size limit, making it vulnerable to denial of service via oversized payloads.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.

7.5

-

Basic Information

Basic Information

Concerned about an active attack path?

GHSA-q447-rj3r-2cgh: OpenClaw affected by denial of service via unbounded webhook request body buffering

Summary

Details

Impact

Patch details (implemented)

Tests

Remediation

Credits

GHSA-q447-rj3r-2cgh:

7.5

-

Basic Information

Basic Information

Is this CVE running in your environment?

Technical Details

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability IntelligenceMiggo AI

Unlock WAF rules for this CVE

WAF Protection Rules

WAF Rule

Reasoning

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

7.5

7.5

GHSA-q447-rj3r-2cgh: OpenClaw affected by denial of service via unbounded webhook request body buffering

Summary

Details

Impact

Patch details (implemented)

Tests

Remediation

Credits

Basic Information

Basic Information

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI