CVE-2026-32011

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.

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).

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2026-32011 has a CVSS score of 7.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.3.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-32011? CVE-2026-32011 is a medium-severity uncontrolled resource consumption vulnerability in openclaw (npm), affecting versions <= 2026.3.1. It is fixed in 2026.3.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2026-32011? CVE-2026-32011 has a CVSS score of 7.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32011? openclaw (npm) versions <= 2026.3.1 is affected.
4. Is there a fix for CVE-2026-32011? Yes. CVE-2026-32011 is fixed in 2026.3.2. Upgrade to this version or later.
5. Is CVE-2026-32011 exploitable, and should I be worried? Whether CVE-2026-32011 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32011 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32011? Upgrade openclaw to 2026.3.2 or later.