# CVE-2026-120263: Gitea OAuth2 account auto-linking takeover through the sign-up form


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-8p3x-w464-4g6v

## What is CVE-2026-120263?

CVE-2026-120263 is a critical vulnerability in Gitea, published on 1 Nov 2026. 

### Official description

When `[oauth2_client].ACCOUNT_LINKING` is set to `auto` (not the default) and registration is enabled, the link-account sign-up form looked up the existing account to link by the user name or email submitted in the form instead of the identity asserted by the OAuth2 provider. An attacker with an account on a configured OAuth2 provider could submit another user's name, link their external identity to that Gitea account and be signed in as it without its password, including as an administrator. The link persisted for later sign-ins. Automatic linking now only happens when the existing account matches the provider's email or provider-derived user name; otherwise the account password is required.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-120263 being exploited?

There is no known exploitation of CVE-2026-120263 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120263 is a critical vulnerability in Gitea, published on 1 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120263 in the wild and no public exploit code.

Affected product: Gitea. 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-120263/ (Markdown: https://insights.sbomify.com/CVE-2026-120263/index.md)
```

## Sources

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

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