Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 01 Nov 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The `/{username}` web route accepted personal access tokens over HTTP Basic authentication without checking their scope. A token confined to an unrelated scope, such as `read:issue`, could read its owner's private activity through the user RSS/Atom feed and the profile activity tab, and other members' activity in a private organization through the organization feed; a public-only token could list the owner's private repositories and organizations and render private profile READMEs. For a site administrator's token this applied to every account. Tokens are now accepted on this route only for feeds, which require `read:user` or `read:organization`. | |
| Title | Gitea user and organization feed token scope bypass | |
| Weaknesses | CWE-863 | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-11-01T09:48:57.404Z
Reserved: 2026-11-01T08:50:49.250Z
Link: CVE-2026-119625
No data.
Status : Deferred
Published: 2026-11-01T10:18:36.937
Modified: 2026-11-01T10:18:37.040
Link: CVE-2026-119625
No data.
OpenCVE Enrichment
Updated: 2026-11-01T11:30:06Z
-
CWE-863
Incorrect Authorization