OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes
euvd · EUVD-2026-58138 · Published
No access to your tenant or devices. Every item links to its source. What this means
OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes
Read the publisher's advisoryOIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes
Read the publisher's advisoryOIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes
Read the publisher's advisory### 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: ```http 403 Forbidden ``` with a scope-related error. However, the same `read:misc` token can be supplied as a bearer credential to: ```http GET /login/oauth/userinfo Authorization: Bearer <token> ``` and receives a successful response containing identity claims. Observed claims include: - `email` - `groups` 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 1. Create a personal access token with only the following scope: ```text read:misc ``` 2. Verify that the token cannot access user-related REST API endpoints: ```http GET /api/v1/user GET /api/v1/user/emails GET /api/v1/user/orgs ``` Each request returns: ```http 403 Forbidden ``` 3. Send the same token to the OIDC userinfo endpoint: ```http GET /login/oauth/userinfo Authorization: Bearer <read-misc-token> ``` 4. Observe that the request succeeds and returns identity claims, for example: ```json { "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.
Read the publisher's advisoryGitea: OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes in gitea.dev
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
euvd · EUVD-2026-58138 · Published
nvd · CVE-2026-55982 · Published
osv · GHSA-mg4f-x9v4-6h2p · Published
osv · GO-2026-6065 · Published
cve-program · CVE-2026-55982 · Published