PT-2026-63277 · Gitea+1 · Gitea+1

·

CVE-2026-50105

·

Published

2026-07-21

·

Updated

2026-08-26

CVSS v3.1

4.3

Medium

VectorAV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Name of the Vulnerable Software and Affected Versions Gitea version 1.26.2
Description RSS and Atom feed handlers fail to enforce token-scope or public-only restrictions when using API-token Basic authentication. This allows a personal access token that is restricted to public-only access or lacks the repository scope to access private content, provided the account owning the token has legitimate read access to the repository. This is a token-confinement bypass that exposes private commit metadata (SHA, full message, author name, and email), private release names, notes, descriptions, private tag names, and the token owner's private activity stream.
API Endpoints:
  • /{owner}/{repo}.rss and /{owner}/{repo}.atom
  • /{owner}/{repo}/rss/branch/* and /{owner}/{repo}/atom/branch/*
  • /{owner}/{repo}/releases.rss and /{owner}/{repo}/releases.atom
  • /{owner}/{repo}/tags.rss and /{owner}/{repo}/tags.atom
  • /{user}.rss and /{user}.atom
Recommendations For Gitea version 1.26.2, implement a token-scope check in the ShowBranchFeed, ShowRepoFeed, ShowFileFeed, and ShowReleaseFeed handlers to ensure tokens are not public-only and possess the required scopes. Additionally, restrict the includePrivate logic in the user feed handler to prevent confined tokens from accessing private activity streams.

Exploit

Fix

Missing Authorization

Information Disclosure

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-50105
GHSA-6CQF-375W-639G
GO-2026-6036
OPENSUSE-SU-2026:21483-1

Affected Products

Gitea
Red Os