CVE-2026-32049: Openclaw Openclaw DOS Vulnerability

CVE-2026-32049 Overview

OpenClaw versions prior to 2026.2.22 contain a resource allocation vulnerability (CWE-770) that fails to consistently enforce configured inbound media byte limits before buffering remote media across multiple channel ingestion paths. Remote attackers can exploit this flaw by sending oversized media payloads to trigger elevated memory usage and potential process instability, leading to denial of service conditions.

Critical Impact

Remote attackers can cause denial of service by bypassing media size limits, resulting in memory exhaustion and service disruption on affected OpenClaw Node.js deployments.

Affected Products

• OpenClaw versions prior to 2026.2.22
• OpenClaw Node.js deployments with multiple channel ingestion paths
• BlueBubbles and MS Teams extension modules

Discovery Timeline

• 2026-03-21 - CVE CVE-2026-32049 published to NVD
• 2026-03-23 - Last updated in NVD database

Technical Details for CVE-2026-32049

Vulnerability Analysis

This vulnerability stems from inconsistent enforcement of inbound media byte limits across different channel ingestion pathways in OpenClaw. When remote media is fetched through various extensions (such as BlueBubbles and MS Teams), the application fails to properly validate and limit the size of incoming media payloads before buffering them into memory.

The flaw allows attackers to bypass configured size restrictions, causing the application to allocate excessive memory when processing oversized media content. This can lead to memory exhaustion, process instability, and ultimately denial of service. The vulnerability is particularly concerning because it can be exploited remotely without authentication through network-accessible media ingestion endpoints.

Root Cause

The root cause is improper resource allocation control (CWE-770: Allocation of Resources Without Limits or Throttling). Multiple channel ingestion paths in OpenClaw do not uniformly enforce the configured max-bytes limit during remote media fetch operations. Each extension module (BlueBubbles, MS Teams, etc.) handles media downloads independently, and some code paths failed to implement proper size validation before buffering the response data.

Attack Vector

The attack vector is network-based, requiring no authentication or user interaction. An attacker can exploit this vulnerability by:

1. Identifying an OpenClaw instance with exposed media ingestion endpoints
2. Crafting or hosting oversized media payloads exceeding configured limits
3. Sending requests that trigger media downloads through vulnerable channel paths
4. The server attempts to buffer the entire oversized payload into memory
5. Repeated attacks exhaust available memory, causing service degradation or crash

The following code snippets show the security patches applied to enforce inbound media max-bytes during remote fetch operations:

BlueBubbles Extension Fix:

 import { resolveBlueBubblesServerAccount } from "./account-resolve.js";
 import { postMultipartFormData } from "./multipart.js";
 import { getCachedBlueBubblesPrivateApiStatus } from "./probe.js";
+import { getBlueBubblesRuntime } from "./runtime.js";
 import { extractBlueBubblesMessageId, resolveBlueBubblesSendTarget } from "./send-helpers.js";
 import { resolveChatGuidForTarget } from "./send.js";
 import {

Source: GitHub Commit Update

MS Teams Extension Fix:

   url: string;
   tokenProvider?: MSTeamsAccessTokenProvider;
   fetchFn?: typeof fetch;
+  requestInit?: RequestInit;
   allowHosts: string[];
   authAllowHosts: string[];
 }): Promise<Response> {
   const fetchFn = params.fetchFn ?? fetch;
-  const firstAttempt = await fetchFn(params.url);
+  const firstAttempt = await fetchFn(params.url, params.requestInit);
   if (firstAttempt.ok) {
     return firstAttempt;
   }

Source: GitHub Commit Update

Detection Methods for CVE-2026-32049

Indicators of Compromise

• Unusual memory consumption spikes on OpenClaw server processes
• Multiple failed or slow media download requests in application logs
• Connection timeouts or service unavailability following media ingestion attempts
• Abnormally large HTTP responses from remote media sources in network logs

Detection Strategies

• Monitor process memory utilization for OpenClaw Node.js instances and alert on abnormal growth patterns
• Implement network-level monitoring for oversized HTTP responses targeting media ingestion endpoints
• Review application logs for repeated media download failures or timeout errors
• Deploy intrusion detection rules to identify unusually large payload transfers to OpenClaw services

Monitoring Recommendations

• Configure resource monitoring dashboards to track memory usage trends on OpenClaw deployments
• Set up alerting thresholds for process memory exceeding normal operational baselines
• Enable detailed logging for media ingestion operations to capture payload size information
• Implement rate limiting on media download endpoints to throttle potential abuse

How to Mitigate CVE-2026-32049

Immediate Actions Required

• Upgrade OpenClaw to version 2026.2.22 or later immediately
• Review and validate inbound media byte limit configurations across all channel ingestion paths
• Implement network-level payload size restrictions as a defense-in-depth measure
• Monitor affected systems for signs of exploitation until patches are applied

Patch Information

The vulnerability has been addressed in OpenClaw version 2026.2.22. The security fix ensures consistent enforcement of inbound media max-bytes limits during remote fetch operations across all extension modules.

• Security Patch: GitHub Commit 73d93dee64127a26f1acd09d0403b794cdeb4f5c
• Security Advisory: GitHub Security Advisory GHSA-rxxp-482v-7mrh
• Technical Details: VulnCheck DoS Advisory

Workarounds

• Implement reverse proxy or WAF rules to enforce strict payload size limits on incoming media requests
• Configure infrastructure-level memory limits and process restart policies for OpenClaw services
• Temporarily disable or restrict access to media ingestion endpoints until patching is complete
• Deploy network segmentation to limit exposure of OpenClaw instances to untrusted networks

# Example: Configure memory limits for Node.js process
export NODE_OPTIONS="--max-old-space-size=512"

# Example: Nginx proxy configuration to limit request body size
# Add to server or location block for OpenClaw media endpoints
client_max_body_size 10M;