TAKO AI Agent for Okta: Authenticated Python execution through validator bypass
Impact
TAKO AI Agent for Okta versions prior to 3.0.1-beta allow authenticated users to execute arbitrary Python code, potentially disclosing environment secrets and exposing the SQLite database. This occurs due to a validator bypass in the `script_code` field of `POST /api/react/execute-script` requests. An attacker with a valid `fctr_session` cookie can exploit this weakness.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.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, any authenticated user with a valid fctr_session cookie can submit arbitrary Python source in the script_code field of POST /api/react/execute-script, without administrator privilege. In src/api/routers/react_stream.py, the source is stored with skip_discovery=True, bypassing AI-based content filtering, and is passed to validate_generated_code in src/utils/security_config.py. BLOCKED_PATTERNS recognizes direct __import__ calls but misses the import name passed as a string, getattr is in ALLOWED_BUILTINS, and the AST checker handles ast.Name and ast.Attribute targets but fails to handle ast.Call targets. Dynamic getattr call chains through __builtins__ therefore evade validation. The _write_temp_script helper writes the accepted code to disk, and asyncio.create_subprocess_exec() executes it as the application process user, which is root in the default container. Command output is returned as Server-Sent Events through GET /api/react/stream-react-updates?process_id=<id>. The resulting container compromise can disclose environment secrets including Okta API tokens and the JWT key, expose the SQLite database, and permit backend-service pivoting and persistence. 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-63378View 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.