CVE-2026-32011: OpenClaw has pre-auth webhook body parsing that can enable unauthenticated slow-request DoS
OpenClaw 2026.3.1 and earlier parsed webhook request bodies for BlueBubbles and Google Chat before checking authentication or signatures. An unauthenticated client can hold the parser open with slow or oversized bodies and degrade availability. Fixed in openclaw 2026.3.2.
Published Mar 3, 2026 · Updated Mar 20, 2026 · Analysis Oct 31, 2026
What an attacker can do
The BlueBubbles and Google Chat webhook handlers read and parsed the full request body first, then ran the authentication and signature checks. Anyone who could reach the webhook endpoint could send a request with a very slow or oversized body and keep the parser busy. Several such connections at once degrade the gateway for real users (CWE-400, CWE-770).
The attacker needs only network access to the webhook port. No credentials, no user interaction. The CVSS 3.1 vector rates availability impact high and confidentiality and integrity none, so there is no data exposure or code execution here.
The practical risk is for gateways that expose these two webhooks to the internet so that BlueBubbles or Google Chat can call in. An outage there cuts off the messaging channels through which people reach the agent. The advisory does not say how many slow connections are needed.
Who is affected
The openclaw npm package at 2026.3.1 and earlier is affected. Only the BlueBubbles and Google Chat webhook paths are named. Check the version:
npm ls openclawIf neither channel is configured on your gateway, these handlers are not in use.
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.3.1
- Fixed in
- 2026.3.2
- Check
npm ls openclaw
How to fix it
Upgrade to openclaw 2026.3.2 or newer.
npm install [email protected]Per the advisory, the fix (commit d3e8b17) enforces auth before body parsing on the affected webhook paths. It adds strict body-size and time budgets before authentication, and shared in-flight request guardrails. Regression tests cover these. The advisory lists no other mitigation.
How to tell if you were hit
Look in reverse-proxy and gateway logs for webhook requests to the BlueBubbles or Google Chat paths that stay open for a long time, send bodies far larger than normal, or arrive in large numbers from a single source without ever authenticating. Symptoms on the host are the gateway answering slowly, or timeouts for legitimate webhook deliveries. The advisory names no log line.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Impact
OpenClaw webhook handlers for BlueBubbles and Google Chat accepted and parsed request bodies before authentication and signature checks on vulnerable releases. This allowed unauthenticated clients to hold parser work open with slow/oversized request bodies and degrade availability (slow-request DoS).
Affected Packages / Versions
- Package:
openclaw(npm) - Affected releases:
<= 2026.3.1 - Latest published vulnerable version at triage time:
2026.3.1(npm) - Fixed release:
2026.3.2(released)
Fix Commit(s)
d3e8b17aa6432536806b4853edc7939d891d0f25
Mitigation
Upgrade to 2026.3.2 (or newer). The fix enforces auth-before-body for affected webhook paths, adds strict pre-auth body/time budgets, and introduces shared in-flight/request guardrails with regression coverage.
Credited to GCXWLP.
Questions
- Does the attacker need credentials?
No. The flaw is that the body is parsed before authentication, so the CVSS vector lists no privileges and no user interaction.
- Which webhooks are affected?
The BlueBubbles and Google Chat webhook handlers in openclaw 2026.3.1 and earlier.
- What does CVE-2026-32011 not allow?
It does not expose data or run code. The advisory describes only a slow-request denial of service.
- Is the fix released?
Yes. openclaw 2026.3.2 is published and enforces auth-before-body with pre-auth body and time budgets.
References
Read for this analysis:
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
