CVE-2026-119625

Gitea user and organization feed token scope bypass

Published Nov 1, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
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`.

Analysis

AI-generated

Technical impact

The vulnerability allows an attacker to submit a personal access token over HTTP Basic authentication to the /{username} route without the system verifying the token's declared scope. A token that should be limited to unrelated scopes, such as read:issue, can therefore be used to read a user's private activity feed and profile activity tab. Tokens with only public permissions can enumerate a user's private repositories and organizations and even render private profile READMEs. Administrators' tokens can affect every account in the same way. Because the attack is performed via standard web requests over HTTP Basic authentication, an attacker only needs to possess any valid token and the target's username to exploit this flaw.

Affected Systems

All Gitea installations running a version prior to the 28.3.0 release are vulnerable. The issue was corrected in release 28.3.0, which now limits token acceptance on the /{username} route to feeds that explicitly declare a read:user or read:organization scope. Site administrators should verify they are running V28.3.0 or later so that this enforcement is active.

Risk and Exploitability

The flaw has a moderate potential impact, with a CVSS score of 4.3, because it allows unauthorized reading of private data without providing code execution or privilege escalation. No published exploit code exists and the EPSS score is < 1%, yet the KEV catalog does not list this vulnerability, indicating it may not have been widely exploited yet. The attack vector is assumed to over standard web requests; an attacker merely needs a user’s open‑API token and knowledge of the target username. Until the patch is applied, any user controlled or leaked token could be used to pull private activity data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Gitea 28.3.0 or later to enforce scope restrictions on the /{username} route.
  • Revoke and regenerate any personal access tokens that were used with the old versions, ensuring they are assigned the minimum required scopes (read:user or read:organization) for feed consumption.
  • Audit repositories and organizations for inadvertent exposure of private activity or README content and rotate tokens if any unauthorized data was accessed.

Generated by OpenCVE AI on November 5, 2026 at 01:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-425
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
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
Weaknesses
  • CWE-425

    Direct Request ('Forced Browsing')

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 6, 2026, 3:07 PM
Reserved
Nov 1, 2026, 8:50 AM
Status
Deferred
Published
Nov 1, 2026, 10:18 AM
Modified
Nov 6, 2026, 3:17 PM
Severity
Moderate
Public date
Nov 1, 2026, 9:48 AM