Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-34511 is a medium-severity Use of Insufficiently Random Values (CWE-330) vulnerability in Openclaw Openclaw. Its CVSS base score is 6.0 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steal Application Access Token (T1528); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as APIs and Models; in the Privacy and Disclosure risk domain.
The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SC-23 (Session Authenticity) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-18849
Vulnerability Data
OpenClaw before 2026.4.2 reuses the PKCE verifier as the OAuth state parameter in the Gemini OAuth flow, exposing it through the redirect URL. Attackers who capture the redirect URL can obtain both the authorization code and PKCE verifier, defeating PKCE…
more
protection and enabling token redemption.
- CWE(s)
AI Security AnalysisAI
- AI Category
- APIs and Models
- Risk Domain
- Privacy and Disclosure
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: gemini
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The PKCE misuse directly enables theft and redemption of OAuth application access tokens via captured redirect URLs.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Requires proper management of authenticators such as the PKCE code_verifier so it is never reused or placed in an exposed redirect URL.
Mandates mechanisms that protect session authenticity, directly addressing the incorrect reuse of the PKCE verifier as the OAuth state parameter.
Enforces that authorization-code redemption succeeds only when the client presents a secret that has not been exposed via the redirect URL.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly enforce use of cryptographically strong RNGs and catch insufficient randomness during design, coding, and testing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Cryptographic controls require use of approved, sufficiently random values for keys and nonces.
Security testing can detect weak randomness but does not prescribe the control itself.
Secure SDLC processes include verification steps that can catch insufficient randomness but do not directly specify RNG requirements.
Secure coding standards explicitly prohibit use of weak or predictable random number generators.
Secure authentication mechanisms depend on unpredictable values (nonces, salts, session tokens) to resist guessing.