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 when the OAuth2 client setting UPDATE_AVATAR is enabled. A user who can control the avatar value (commonly the OIDC picture claim) from a configured OAuth2 or OIDC provider can make the Gitea server send outbound GET requests to arbitrary addresses, including internal and cloud metadata endpoints, which is a blind server-side request forgery. Upgrade to Gitea 1.27.0 or later; the source does not describe another 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 |
|---|---|---|---|---|
| 3.1 | Low | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0029, the 21st percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:55 UTC First seen by agentprime
- 31 Oct 2026, 14:55 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-x77v-q46j-393g
- OSV: GHSA-x77v-q46j-393g
- github.com/go-gitea/gitea/security/advisories/GHSA-x77v-q46j-393g
- 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