# CVE-2026-63203: Logto: Account API can disclose stored third-party provider tokens without the identities scope

> Attackers with low-privilege tokens can retrieve stored third-party provider tokens due to missing scope checks, enabling access to upstream APIs.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-6g9q-qrx7-3jxf

## What is CVE-2026-63203?

CVE-2026-63203 is a high-severity missing authorization vulnerability in logto-io logto, published on 24 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Logto is the modern, open-source auth infrastructure for SaaS and AI apps. From 1.31.0 until 1.42.0, the Account API handlers in packages/core/src/routes/account/third-party-tokens.ts allow a caller holding a same-user access token with only the openid scope to retrieve stored social or enterprise SSO provider access tokens through GET /api/my-account/identities/{target}/access-token or GET /api/my-account/sso-identities/{connectorId}/access-token. The handlers authenticate the user but do not require the identities scope that protects neighboring identity-detail operations, bypassing the intended Account API consent boundary. Exploitation requires federated token-set storage to be enabled and the affected user to have authenticated through a supported connector. A low-trust application can use the disclosed provider token against upstream APIs within that token's granted scopes. This issue is fixed in version 1.42.0.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-63203?


## How do I fix CVE-2026-63203?

No fix has been published for CVE-2026-63203 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63203 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63203 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63203 and fix it if it is affected.

What it is: CVE-2026-63203 is a high-severity missing authorization vulnerability in logto-io logto, published on 24 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63203 exists.

Affected product: logto-io logto. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63203/ (Markdown: https://insights.sbomify.com/CVE-2026-63203/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63203
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63203
- OSV: https://osv.dev/vulnerability/CVE-2026-63203

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63203/
Summaries are generated and may contain mistakes; the official description above is the record.