CVE-2026-55982: Gitea: OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes
Summary The OIDC userinfo endpoint (GET /login/oauth/userinfo) accepts Gitea API tokens as bearer credentials but does not enforce API token scopes before returning identity claims. A personal access token scoped only to read:misc can successfully retrieve user information from the OIDC userinfo endpoint, even though the same token is denied access to user-related REST API endpoints that enforce scope checks.
Published Jul 21, 2026
Affected packages
code.gitea.io/gitea
- Ecosystem
- Go
- Affected
- < 1.27.0
- Fixed in
- 1.27.0
- Check
go list -m code.gitea.io/gitea
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The OIDC userinfo endpoint (GET /login/oauth/userinfo) accepts Gitea API tokens as bearer credentials but does not enforce API token scopes before returning identity claims.
A personal access token scoped only to read:misc can successfully retrieve user information from the OIDC userinfo endpoint, even though the same token is denied access to user-related REST API endpoints that enforce scope checks.
As a result, identity information remains accessible through the OIDC endpoint regardless of the scopes assigned to the API token.
Details
Gitea supports scoped personal access tokens and enforces scope checks on user-related REST API endpoints.
For example, a token scoped only to read:misc is denied access to endpoints such as:
| Endpoint | Required Scope | | `GET /api/v1/user` | `read:user` | | `GET /api/v1/user/emails` | `read:user` | | `GET /api/v1/user/orgs` | `read:organization` |
Requests to these endpoints return:
403 Forbiddenwith a scope-related error.
However, the same read:misc token can be supplied as a bearer credential to:
GET /login/oauth/userinfo
Authorization: Bearer <token>and receives a successful response containing identity claims.
Observed claims include:
emailgroups
The groups claim contains organization and team membership information associated with the authenticated user.
This behavior indicates that the OIDC userinfo endpoint accepts API tokens but does not apply scope restrictions before returning identity claims.
PoC
PoC Details
Proof-of-concept code: https://anonymous.4open.science/r/Gitea_PoC-EC93/3_poc_oidc_userinfo_scope_bypass
Reproduction Steps
- Create a personal access token with only the following scope:
read:misc- Verify that the token cannot access user-related REST API endpoints:
GET /api/v1/user
GET /api/v1/user/emails
GET /api/v1/user/orgsEach request returns:
403 Forbidden- Send the same token to the OIDC userinfo endpoint:
GET /login/oauth/userinfo
Authorization: Bearer <read-misc-token>- Observe that the request succeeds and returns identity claims, for example:
{
"email": "[email protected]",
"groups": [
...
]
}Impact
Holders of narrowly scoped API tokens can obtain identity information through the OIDC userinfo endpoint regardless of the scopes assigned to the token.
The issue does not provide access to repositories, issues, pull requests, administrative functionality, or data belonging to other users.
Impact is limited to disclosure of identity information associated with the authenticated user. However, it weakens the authorization boundary established by API token scopes because identity claims remain accessible even when the token lacks user- or organization-related scopes.
Credited to ybsun0215.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-20779
Gitea: TOTP TOCTOU race on web 2FA paths + missing replay check on Basic-Auth `X-Gitea-OTP` surface
high7.1Jul 21, 2026CVE-2026-20896
Gitea Docker image: `REVERSE_PROXY_TRUSTED_PROXIES = *` default lets any source IP impersonate any user via `X-WEBAUTH-USER`
critical9.8Jul 21, 2026CVE-2026-22874
Gitea: Incomplete SSRF Protection in Webhook and Migration Allow-list Default Filter
critical9.6Jul 21, 2026CVE-2026-23603
Gitea: Blind SSRF in OAuth2 avatar synchronization via unvalidated OIDC picture claim
low3.1Jul 21, 2026CVE-2026-24451
Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private
high7.5Jul 21, 2026CVE-2026-25038
Gitea: Unauthorized Access to Labels of Private Organizations
high7.5Jul 21, 2026
