# CVE-2026-82263: Logto Server-Side Request Forgery via OIDC SSO Connector Issuer URL

> Tenant administrators can exploit an SSRF vulnerability in Logto's OIDC connector to access internal network services and read response data.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-2c8c-r4jf-gp34

## What is CVE-2026-82263?

CVE-2026-82263 is a high-severity server-side request forgery vulnerability in logto-io logto, published on 28 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Logto through 1.42.0 contains a server-side request forgery vulnerability in the OIDC SSO connector creation endpoint that fails to validate the issuer URL parameter. Tenant administrators with Management API credentials can supply arbitrary internal URLs to trigger HTTP GET requests to private network services, with response content returned in API responses.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-82263 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82263 is a high-severity server-side request forgery vulnerability in logto-io logto, published on 28 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82263 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-82263/ (Markdown: https://insights.sbomify.com/CVE-2026-82263/index.md)
```

## Sources

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

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