OpenClaw before 2026.3.12 applies rate limiting only after successful webhook authentication, allowing attackers to bypass rate limits and brute-force webhook secrets. Attackers can submit repeated authentication requests with invalid secrets without triggering rate limit responses, enabling systematic secret guessing and subsequent forged webhook submission.
Security readout for executives and security teams
Plain-English summary
OpenClaw versions before 2026.3.12 may let unauthenticated attackers repeatedly guess webhook secrets without hitting rate limits. If a secret is guessed, attackers could submit forged webhooks. The issue is medium severity because it depends on secret guessing but affects an internet-reachable authentication boundary.
Executive priority
Prioritize remediation for internet-facing OpenClaw webhook deployments. Treat this as a targeted integrity risk rather than a broad system compromise issue unless logs show suspicious activity.
Technical view
The flaw is a CWE-307 improper restriction of authentication attempts. OpenClaw applied rate limiting only after successful webhook authentication, so failed pre-authentication secret checks did not consume rate-limit budget. CVSS 4.0 is 6.9 with network attack vector, low complexity, no privileges, and limited confidentiality and integrity impact.
Likely exposure
Exposure is most likely for organizations running OpenClaw before 2026.3.12 with webhook endpoints reachable by untrusted networks or the public internet.
Exploitation context
The bundle does not report active exploitation, and KEV status is false. Exploitation would require repeated webhook secret guessing and then use of a valid secret to forge webhook submissions.
Researcher notes
Key validation points are rate-limit placement and failed authentication handling before webhook secret validation succeeds. Avoid assuming broader product impact beyond OpenClaw before 2026.3.12 based on the supplied sources.
Mitigation direction
Upgrade OpenClaw to 2026.3.12 or later.
Review the GitHub advisory for vendor-specific remediation details.
Restrict webhook endpoint exposure where operationally possible.
Review webhook secrets if suspicious failed authentication patterns appear.
Monitor for unexpected webhook-triggered actions.
Validation and detection
Inventory OpenClaw deployments and confirm versions are before or after 2026.3.12.
Identify webhook endpoints reachable from public or untrusted networks.
Review logs for repeated failed webhook authentication attempts.
After upgrade, confirm failed webhook authentication is rate-limited.
Check application records for unexpected webhook-driven changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-307: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-307 · source CWE mapping
Improper Restriction of Excessive Authentication Attempts
Improper Restriction of Excessive Authentication Attempts represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.