Skip to main content
VulnerabilityPublished

CVE-2026-63377: fctr-id okta-ai-agent · Missing Authentication for Critical Functionality

Affects fctr-id okta-ai-agentSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.0.1-beta as a priority.

Data as of 30 Oct 2026, 23:20 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.8
Patch
Available – fixed in 3.0.1-beta
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade fctr-id okta-ai-agent to 3.0.1-beta.

Affected software

ProductAffectedFixed in
fctr-idokta-ai-agentAffected
  • <3.0.1-beta
Fixed in
  • 3.0.1-beta

AI-suggested

Upgrade to version 3.0.1-beta or later, where this vulnerability is fixed. The vendor has addressed the missing authentication on the initial setup endpoint.

Description

CVE-2026-63377 is a critical authentication bypass vulnerability in TAKO AI Agent for Okta versions prior to 3.0.1-beta. It allows an unauthenticated network attacker to create the first administrator account by accessing the POST /api/auth/setup endpoint before the legitimate owner completes initial setup. The flaw arises because the setup endpoint does not require authentication or a bootstrap token and is exposed on all network interfaces by default. Exploitation grants full administrative control, enabling data access, user and configuration modification, and denial of legitimate setup. The issue is fixed in version 3.0.1-beta.

References

Community reviews

Loading reviews…