Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Gitea versions before 1.27.0 are affected. An attacker holding a restricted access token can send it through Basic authentication to bypass the check that requires password login on the token creation endpoint, then create a new token with any scope, including all scopes, without knowing the account password. Upgrade to Gitea 1.27.0 or later; the source lists no workaround.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.8 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | ADP (CISA-ADP) |
- CISA KEV Not listed.
- EPSS 0.0083, the 58th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:57 UTC First seen by agentprime
- 31 Oct 2026, 14:57 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-683j-3ff6-hh2x
- OSV: GHSA-683j-3ff6-hh2x
- github.com/go-gitea/gitea/security/advisories/GHSA-683j-3ff6-hh2x
- github.com/go-gitea/gitea/pull/38406
- github.com/go-gitea/gitea/pull/38426
- github.com/go-gitea/gitea/commit/de4b8277e9cb576f2315fb03b5ab6478b42a1d31
- github.com/go-gitea/gitea/commit/f69e15afe7496cc62e96dab244629c69eb31a7bf
- github.com/go-gitea/gitea
- github.com/go-gitea/gitea/releases/tag/v1.27.0