Is CVE-2026-100571 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-100571 being exploited in the wild.

How severe is CVE-2026-100571?

Medium severity, with a CVSS score of 5.3, published 26 September 2026.

Which products and versions are affected?

Openclaw >=2026.6.6, <2026.8.1.

Is there a fix for CVE-2026-100571?

A patch was published on 2026-09-11: Fixed in version 2026.8.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-100571 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-100571?

Check whether you run Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-100571: OpenClaw SMS webhook rate limit bypass

Q: Which products and versions are affected?

Openclaw >=2026.6.6, <2026.8.1.

Q: Is there a fix for CVE-2026-100571?

A patch was published on 2026-09-11: Fixed in version 2026.8.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-100571 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-100571?

Check whether you run Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-100571 · Severity: medium · CVSS 5.3 · Published 2026-09-26

OpenClaw is a Node.js package that handles SMS webhooks from Twilio, a service that sends and receives text messages. In affected versions, the rate limiting check runs before signature verification, allowing an attacker to flood the system with invalid requests and block legitimate incoming SMS messages. The attack only works when multiple clients share a network connection through a proxy, and while no messages can be forged or read, SMS delivery will be temporarily lost.

Technologies: Openclaw. Vendors: Openclaw.

Quick answers

Is CVE-2026-100571 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-100571 being exploited in the wild.
How severe is CVE-2026-100571?: Medium severity, with a CVSS score of 5.3, published 26 September 2026.
Which products and versions are affected?: Openclaw >=2026.6.6, <2026.8.1.
Is there a fix for CVE-2026-100571?: A patch was published on 2026-09-11: Fixed in version 2026.8.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-100571 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-100571?: Check whether you run Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an uncontrolled resource consumption issue (CWE-400) where the SMS webhook applies rate limits based on the raw socket address before verifying the Twilio signature. An unauthenticated remote attacker can exhaust the pre-auth rate limit bucket with invalid requests over the network, causing subsequent valid signed callbacks to receive HTTP 429 responses. This denial-of-service impact is limited to temporary inbound SMS loss and does not allow callback forgery or data access; the fix is to verify signature before rate limiting.

Affected products

OpenClaw openclaw >=2026.6.6, <2026.8.1

Timeline

2026-09-26: disclosed
2026-09-11: patched: Fixed in version 2026.8.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.