CVE-2026-100600: ClawHub before 8c2de6c506 Quota Exhaustion via Anonymous API
ClawHub (the openclaw/clawhub application/backend) does not bind anonymous HTTP API requests to a trusted caller identity, so all direct anonymous API requests share a single default quota allowance. A remote, unauthenticated caller can drain that shared allowance and thereby deny or degrade API access for unrelated visitors. In addition, when the TRUSTFORWARDEDIPS option is enabled without an authenticated edge/proxy, clients can supply arbitrary forwarded IP headers to select quota identities of their choosing and evade rate limiting. The issue was confirmed at revision cbfee7343ddc867316dd9b3de6fa8856730f9f41; the complete historical affected range was not established. It is fixed in revision 8c2de6c506bb4efabe3f0c2ffb8370b9e23d4650 (PR #3684), where direct anonymous calls are redirected to the public API origin without consuming quota and forged identity assertions return HTTP 401. The npm CLI and OpenClaw runtime are separate products and are not affected.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openclaw/clawhubto a version that resolves this vulnerability.Patch 8c2de6c506bb4efabe3f0c2ffb8370b9e23d4650
Event History
Frequently Asked Questions
Which deployments and products are affected?
The issue affects the OpenClaw ClawHub application/backend. The npm CLI and the OpenClaw runtime are separate products and are not affected.
When can forwarded IP headers be used to evade rate limiting?
This occurs when TRUST_FORWARDED_IPS is enabled without an authenticated edge or proxy. In that configuration, clients can provide arbitrary forwarded-IP headers and choose quota identities.
How can I determine whether a ClawHub deployment is fixed?
The issue was confirmed at revision cbfee7343ddc867316dd9b3de6fa8856730f9f41 and is fixed in revision 8c2de6c506bb4efabe3f0c2ffb8370b9e23d4650. The complete historical affected range has not been established.
What can be done if updating is not immediately possible?
Do not enable TRUST_FORWARDED_IPS unless requests pass through an authenticated edge or proxy. This prevents clients from supplying arbitrary forwarded-IP headers to select quota identities, but direct anonymous requests still share the default quota allowance until the fix is deployed.