CVE-2026-63377

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-114541 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 30, 2026

Last Modified

November 5, 2026

Advisory Details (3)

Auto-updated Nov 7, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Unauthenticated First-Run Admin Takeover via POST /api/auth/setup · Advisory · fctr-id/okta-ai-agent · GitHub

https://github.com/fctr-id/okta-ai-agent/security/advisories/GHSA-536w-42p8-3qv9
GitHub release Patch Available

"Secure the Harness"

Patch available: fctr-id/okta-ai-agent v3.0.1-beta

https://github.com/fctr-id/okta-ai-agent/releases/tag/v3.0.1-beta
GitHub commit Patch Available

commit 3b5ccaff8423 (fctr-id/okta-ai-agent)

Patch available: fctr-id/okta-ai-agent v3.0.1-beta (contains commit 3b5ccaff8423)

https://github.com/fctr-id/okta-ai-agent/commit/3b5ccaff8423cdfa6d26f5e133c01b8b71148df4

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 17× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-11-12 16:34 UTCEchelonGraph re-scored
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-11-11 14:41 UTCEchelonGraph re-scored
  6. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-11-10 12:49 UTCEchelonGraph re-scored
  8. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-11-09 10:57 UTCEchelonGraph re-scored
  10. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-11-08 09:05 UTCEchelonGraph re-scored
  12. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-11-07 07:12 UTCEchelonGraph re-scored
  14. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-11-06 14:55 UTCOSV refresh
  16. 2026-11-06 05:18 UTCEchelonGraph re-scored
  17. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-11-05 03:26 UTCEchelonGraph re-scored
  19. 2026-11-05 03:04 UTCEchelonGraph re-scored
  20. 2026-11-04 23:32 UTCEchelonGraph re-scored
  21. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-11-03 21:39 UTCEchelonGraph re-scored
  23. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-11-02 19:46 UTCEchelonGraph re-scored
  25. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 8 more
  1. 2026-11-02 03:10 UTCEchelonGraph re-scored
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-11-01 01:19 UTCEchelonGraph re-scored
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-31 00:02 UTCENISA EUVD ID recordedEUVD-2026-114541 · Source: ENISA EUVD
  6. 2026-10-30 23:26 UTCEchelonGraph re-scored
  7. 2026-10-30 22:24 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  8. 2026-10-30 22:24 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63377?
CVE-2026-63377 is a critical-severity vulnerability; its CVE record was published on October 30, 2026. 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…
When was the CVE record for CVE-2026-63377 published?
The CVE record for CVE-2026-63377 was published on October 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-63377 actively exploited?
CVE-2026-63377 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63377?
CVE-2026-63377 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63377?
A fix for CVE-2026-63377 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63377

Explore →

Is Your Infrastructure Affected by CVE-2026-63377?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs