Rate-limit bypass via concurrent authentication attempts
Published Apr 28, 2026 · Updated Apr 28, 2026
Race condition in OpenClaw before 2026.4.4 allows remote attackers to bypass shared-secret rate limits via concurrent requests. The asynchronous Gateway authorization path checks a per-key budget without serializing the complete authentication attempt, so parallel requests can consume the same apparent allowance. Exploitation requires network access to a Tailscale-capable path and increases opportunities to guess a valid shared secret; it does not itself authenticate the attacker.
Summary
What happened
Race condition in OpenClaw before 2026.4.4 allows remote attackers to bypass shared-secret rate limits via concurrent requests. The asynchronous Gateway authorization path checks a per-key budget without serializing the complete authentication attempt, so parallel requests can consume the same apparent allowance. Exploitation requires network access to a Tailscale-capable path and increases opportunities to guess a valid shared secret; it does not itself authenticate the attacker.
The record
- CVE
- CVE-2026-41913
- Published
- Apr 28, 2026
- Updated
- Apr 28, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-362, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2026CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.4.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo