Which versions of OpenClaw are affected by EUVD-2026-26112?

OpenClaw versions prior to 2026.3.31 contain a resource exhaustion vulnerability that allows unauthenticated remote attackers to crash servers through malicious Microsoft Teams webhook payloads,…. A patch is available.

How to fix or mitigate EUVD-2026-26112?

Within 24 hours: inventory all OpenClaw deployments and verify current versions. Within 7 days: apply vendor patch via GitHub commit 3834d47 to upgrade all instances to version 2026.3.31 or later, and validate patch deployment in non-production environments first. Within 30 days: conduct post-patch verification testing and review webhook ingestion logs for anomalous activity during the exposure window.

OpenClaw EUVD-2026-26112

Q: What is the CVSS score of EUVD-2026-26112?

EUVD-2026-26112 has a CVSS 4.0 base score of 8.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

| CVE-2026-41405 HIGH

Incorrect Behavior Order: Early Amplification (CWE-408)

2026-04-28 VulnCheck

Denial Of Service Openclaw

8.7

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

8.7 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Re-analysis Queued

Apr 28, 2026 - 20:23 vuln.today

cvss_changed

Analysis Generated

Apr 28, 2026 - 20:06 vuln.today

CVSS changed

Apr 28, 2026 - 19:52 NVD

7.5 (HIGH) 8.7 (HIGH)

EUVD ID Assigned

Apr 28, 2026 - 19:30 euvd

EUVD-2026-26112

Analysis Generated

Apr 28, 2026 - 19:30 vuln.today

Patch released

Apr 28, 2026 - 19:30 nvd

Patch available

CVE Published

Apr 28, 2026 - 18:10 nvd

HIGH 8.7

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on openclaw (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.3.31.

DescriptionCVE.org

OpenClaw before 2026.3.31 parses MS Teams webhook request bodies before performing JWT validation, allowing unauthenticated attackers to trigger resource exhaustion. Remote attackers can send malicious Teams webhook payloads to exhaust server resources by bypassing authentication checks.

AnalysisAI

Resource exhaustion in OpenClaw before 2026.3.31 allows remote unauthenticated attackers to crash servers by sending malicious Microsoft Teams webhook payloads. The application parses request bodies before performing JWT validation, enabling attackers to bypass authentication and trigger denial-of-service conditions. A vendor patch is available via GitHub commit 3834d47, with no evidence of active exploitation (not in CISA KEV) and no public POC identified at time of analysis.

Technical ContextAI

OpenClaw is an application that processes Microsoft Teams webhook integrations. The vulnerability (CWE-408: Incorrect Behavior Order) stems from the application's request processing flow, where computationally expensive parsing operations execute before authentication validation occurs. This design flaw violates secure coding principles that mandate early authentication checks before resource-intensive operations. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N) indicates trivial remote exploitation requiring no user interaction or credentials, though impact is limited to availability (VA:H) with no confidentiality or integrity effects. The JWT validation mechanism that should protect the webhook endpoint is rendered ineffective by premature body parsing.

RemediationAI

Upgrade to OpenClaw version 2026.3.31 or later, which implements JWT validation before request body parsing per GitHub commit 3834d47099dd13c8244ed6de8b9ea9855c553623 (https://github.com/openclaw/openclaw/commit/3834d47099dd13c8244ed6de8b9ea9855c553623). If immediate patching is not feasible, implement network-layer rate limiting on Teams webhook endpoints to cap requests per source IP (e.g., 10 requests/minute), though this reduces attack impact but does not eliminate the vulnerability. Deploy web application firewall rules to enforce maximum request body sizes for webhook paths (recommendation: limit to 1MB or application-specific threshold) to bound resource consumption per request, accepting trade-off that legitimate large payloads may be rejected. Restrict webhook endpoint access to Microsoft Teams IP ranges via firewall rules, available from Microsoft's published service IP lists, noting this assumes trust in source IP validation and does not prevent attacks from compromised Teams accounts. Full vendor advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-p464-m8x6-vhv8.