CSRF in Obot-Platform Obot
CVE-2026-114662
Obot before 0.26.0 contains an authentication bypass vulnerability in the CLI login flow that allows unauthenticated attackers to steal API keys by choosing token request IDs. Attackers can create a token request via POST /api/token-request, send the login link to a signed-in user, and fetch the resulting non-expiring API key to take over the victim's account.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/obot-platform/obot/security/advisories/GHSA-2qcm-3gv6-2mfc (vendor-advisory)
- www.vulncheck.com/advisories/obot-before-0.26.0-api-key-theft-via-cli-login-tok… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-114662?
- CVE-2026-114662 is a high-severity vulnerability in Obot-Platform Obot, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.1/10. Published 2026-10-22.
- How severe is CVE-2026-114662?
- High severity. CVSS v3 base score is 8.1 out of 10.