CVE-2026-28477
OAuth State Validation Bypass in OpenClaw Enables CSRF Attack
Publication date: 2026-03-05
Last updated on: 2026-03-17
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.14 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions prior to 2026.2.14 and involves an OAuth state validation bypass in the manual Chutes login flow.
It allows attackers to bypass Cross-Site Request Forgery (CSRF) protection by convincing a user to paste attacker-controlled OAuth callback data.
This enables the attacker to substitute credentials and maintain token persistence for unauthorized accounts.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access by allowing attackers to bypass CSRF protections and substitute credentials.
This means attackers can persist tokens for unauthorized accounts, potentially gaining access to user accounts or sensitive information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know