What is the CVSS score of CVE-2026-32049?

CVE-2026-32049 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.1%.

Which versions of Openclaw are affected by CVE-2026-32049?

OpenClaw deployments are vulnerable to denial-of-service attacks that could render the application unavailable to users.. A patch is available.

Is there a public PoC exploit available for CVE-2026-32049?

Yes, a public proof-of-concept exploit is available for CVE-2026-32049. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2026-32049?

Within 24 hours: Inventory all OpenClaw instances and confirm versions; assess whether systems process untrusted media uploads from external sources. Within 7 days: Apply vendor patch to upgrade all affected instances to version 2026.2.22 or later in a staged manner, starting with production systems. Within 30 days: Validate patch deployment across all environments and document completion in your patch management system.

Openclaw CVE-2026-32049

EUVD-2026-13945 HIGH

Allocation of Resources Without Limits or Throttling (CWE-770)

2026-03-21 VulnCheck

GHSA-xq3g-m3j8-2vmm

GHSA-rxxp-482v-7mrh

Denial Of Service Openclaw

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

PoC Detected

Mar 23, 2026 - 17:09 vuln.today

Public exploit code

EUVD ID Assigned

Mar 21, 2026 - 01:00 euvd

EUVD-2026-13945

Analysis Generated

Mar 21, 2026 - 01:00 vuln.today

Patch released

Mar 21, 2026 - 01:00 nvd

Patch available

CVE Published

Mar 21, 2026 - 00:42 nvd

HIGH 7.5

DescriptionCVE.org

OpenClaw versions prior to 2026.2.22 fail to consistently enforce configured inbound media byte limits before buffering remote media across multiple channel ingestion paths. Remote attackers can send oversized media payloads to trigger elevated memory usage and potential process instability.

AnalysisAI

OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consistently enforce configured inbound media byte limits across multiple channel ingestion paths. Remote unauthenticated attackers can exploit this by sending oversized media payloads to cause elevated memory consumption and process instability, leading to denial of service. The vulnerability has a CVSS score of 7.5 (High severity) with network-based attack vector and low complexity, though no active exploitation (KEV) or public proof-of-concept has been reported at this time.

Technical ContextAI

OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) is affected by CWE-770 (Allocation of Resources Without Limits or Throttling), indicating a failure to properly constrain resource consumption. The vulnerability stems from inconsistent enforcement of byte limit configurations across multiple media ingestion pathways, allowing certain code paths to buffer remote media content without applying the configured constraints. This architectural flaw in input validation enables attackers to bypass intended resource allocation controls, forcing the application to consume excessive memory when processing specially crafted media payloads through vulnerable channel endpoints.

RemediationAI

Upgrade OpenClaw to version 2026.2.22 or later, which contains the fix for the media byte limit enforcement issue as documented in the vendor security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-rxxp-482v-7mrh and the patch commit at https://github.com/openclaw/openclaw/commit/73d93dee64127a26f1acd09d0403b794cdeb4f5c. Until patching is feasible, implement network-level rate limiting and request size restrictions on media ingestion endpoints using a web application firewall or reverse proxy to constrain maximum upload sizes. Monitor memory consumption patterns for anomalies and configure process restart policies to maintain service availability if resource exhaustion occurs.