CVE-2026-35665

OpenClaw has incomplete Fix for CVE-2026-32011: Feishu Webhook Pre-Auth Body Parsing DoS (Slow-Body / Slowloris Variant)

An unauthenticated attacker can cause a Denial of Service against any OpenClaw instance running the Feishu channel in webhook mode. The Feishu webhook endpoint must be publicly accessible for Feishu to deliver webhooks, so the attacker can directly target it.

With ~50 concurrent slow HTTP connections (each trickling 1 byte/second), the attacker can:

• Exhaust the server's connection handling capacity for 30 seconds per wave
• Block legitimate Feishu webhook deliveries (messages not reaching the bot)
• Consume up to 50MB of memory (50 × 1MB buffer) per attack wave

The attack is trivial, it only requires sending slow HTTP POST requests. No valid Feishu webhook signature or any other credentials are needed.

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

CVE-2026-35665 has a CVSS score of 5.3 (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.24); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-35665? CVE-2026-35665 is a medium-severity uncontrolled resource consumption vulnerability in openclaw (npm), affecting versions < 2026.3.24. It is fixed in 2026.3.24. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2026-35665? CVE-2026-35665 has a CVSS score of 5.3 (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-35665? openclaw (npm) versions < 2026.3.24 is affected.
4. Is there a fix for CVE-2026-35665? Yes. CVE-2026-35665 is fixed in 2026.3.24. Upgrade to this version or later.
5. Is CVE-2026-35665 exploitable, and should I be worried? Whether CVE-2026-35665 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-35665 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-35665? Upgrade openclaw to 2026.3.24 or later.