CVE-2026-120263
Gitea OAuth2 account auto-linking takeover through the sign-up form
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.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: GiteaFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: GiteaFix
gitea.dev (go): GitHub reports patched versions 28.3.0. Check the advisory for the affected release branch.
Source: GitHub GHSA-8p3x-w464-4g6vAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Gitea Gitea gitea.dev
|
≥ 0; < 28.3.0 (affected, semver)
Other versions: unaffected |
CNA: Gitea |
gitea.devgitea.dev
go |
<= 28.2.0 (affected, GitHub advisory range) | GitHub GHSA-8p3x-w464-4g6v |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 9.8 critical |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | ADP: CISA-ADP |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/go-gitea/gitea/security/advisories/GHSA-8p3x-w464-4g6vCNA: Gitea · vendor-advisory
- https://github.com/go-gitea/gitea/pull/40121CNA: Gitea · patch
- https://github.com/go-gitea/gitea/pull/40137CNA: Gitea · patch
- https://blog.gitea.com/release-of-28.3.0/CNA: Gitea · release-notes
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0CNA: Gitea · release-notes
- https://blog.gitea.com/release-of-28.3.0/88ee5874-cf24-4952-aea0-31affedb7ff2
- https://github.com/go-gitea/gitea/pull/4012188ee5874-cf24-4952-aea0-31affedb7ff2
- https://github.com/go-gitea/gitea/pull/4013788ee5874-cf24-4952-aea0-31affedb7ff2
- https://github.com/go-gitea/gitea/releases/tag/v28.3.088ee5874-cf24-4952-aea0-31affedb7ff2
- https://github.com/go-gitea/gitea/security/advisories/GHSA-8p3x-w464-4g6v88ee5874-cf24-4952-aea0-31affedb7ff2
- https://github.com/go-gitea/gitea/security/advisories/GHSA-8p3x-w464-4g6vGitHub Security Advisories · advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.