Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes

cve-program · severity unknownEUVD CVSS 3.1 9.1 CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 9.1 CRITICALCVSS_V4 Publisher rating MODERATEFixed by code.gitea.io/gitea 1.27.0osv · severity unknownFixed by gitea.dev 1.27.0KEV status unknown

cve-program · CVE-2026-55982

Published

OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes

Read the publisher's advisory

euvd · EUVD-2026-58138

Published

OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes

Read the publisher's advisory

nvd · CVE-2026-55982

Published

OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes

Read the publisher's advisory

osv · GHSA-mg4f-x9v4-6h2p

Published

### 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 advisory

osv · GO-2026-6065

Published

Gitea: OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes in gitea.dev

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-55982

Published

Gitea Open Source Git Server

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "Gitea",
                    "product": "Gitea Open Source Git Server",
                    "versions": [
                        {
                            "version": "1.26.2",
                            "status": "affected",
                            "versionType": "semver"
                        }
                    ],
                    "defaultStatus": "unaffected"
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-58138

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 13, 2026, 4:44:40 PM

dateUpdated: Aug 14, 2026, 5:42:09 PM

1 related source bulletins · separate from aliases

WID-SEC-W-2026-2304: Gitea: Mehrere Schwachstellen

CVE-2026-58417 · CVE-2026-58420 · CVE-2026-58425 · CVE-2026-58427 · CVE-2026-58428 · CVE-2026-58429 · CVE-2026-58431 · CVE-2026-58432 · CVE-2026-58433 · CVE-2026-58434 · CVE-2026-58435 · CVE-2026-58436 · CVE-2026-58437 · CVE-2026-58438 · CVE-2026-58439 · CVE-2026-58440 · CVE-2026-58441 · CVE-2026-58442 · CVE-2026-58443 · CVE-2026-58444 · CVE-2026-58445 · CVE-2026-58507 · CVE-2026-58508 · CVE-2026-58510 · CVE-2026-58511 · CVE-2026-59763 · CVE-2026-59765 · CVE-2026-59766 · CVE-2026-23603 · CVE-2026-42931 · CVE-2026-50105 · CVE-2026-54481 · CVE-2026-55982 · CVE-2026-55984 · CVE-2026-55986 · CVE-2026-55987 · CVE-2026-56443 · CVE-2026-56654 · CVE-2026-56657 · CVE-2026-56750 · CVE-2026-56755 · CVE-2026-57886 · CVE-2026-57894 · CVE-2026-57897 · CVE-2026-58314 · CVE-2026-58416

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-55982

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-200

Original publisher date fields

published: 2026-08-13T17:17:24.750

lastModified: 2026-08-26T16:53:48.300

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-mg4f-x9v4-6h2p

Published

code.gitea.io/gitea

Go

SEMVER · introduced 0 → fixed 1.27.0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2026-6065

Published

gitea.dev

Go

SEMVER · introduced 0 → fixed 1.27.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Nov 21:09 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current