TAKO AI Agent for Okta: Unauthenticated first-run administrator takeover
Impact
TAKO AI Agent for Okta versions prior to 3.0.1-beta are vulnerable to unauthenticated administrator takeover via the `POST /api/auth/setup` endpoint. An attacker with network access can create the first administrator account, gaining control and access to sensitive data.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.The initial_setup function checks only the is_setup completion flag and requires no authentication, one-time bootstrap token, or network restriction. Localhost-only CORS rules do not restrict non-browser HTTP clients, and the setup operation does not require access to a real Okta tenant.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
fctr-id · GitHub_M
okta-ai-agent
1 range
fctr-id · GitHub_M
okta-ai-agent
Compare with this publisher’s ranges. This does not inspect your installation.
affected
< 3.0.1-beta
Other versions: unknown
Original source description
TAKO AI Agent for Okta is a local-first AI agent that helps Okta administrators query tenant data using natural language. Prior to 3.0.1-beta, POST /api/auth/setup in src/api/routers/auth.py allows an unauthenticated network attacker to create the first administrator account before the legitimate owner completes initial setup. The initial_setup function checks only the is_setup completion flag and requires no authentication, one-time bootstrap token, or network restriction. The default docker-compose.yml publishes port 8001 on all interfaces, the Dockerfile starts the listener on 0.0.0.0, and src/api/main.py mounts the authentication router without a global authentication guard. The endpoint invokes create_auth_user with UserRole.ADMIN and set_auth_cookie, issuing a valid fctr_session JWT cookie. Localhost-only CORS rules do not restrict non-browser HTTP clients, and the setup operation does not require access to a real Okta tenant. The attacker becomes the sole administrator and prevents legitimate first-run setup, can read Okta-synced user data, API tokens, chat history, and application configuration, modify users and Okta integration credentials, and lock out administrators or disable the service. Already completed setup is rejected. This issue is fixed in version 3.0.1-beta.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-63377View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.