PT-2026-63277 · Gitea+1 · Gitea+1
CVSS v3.1
4.3
Medium
| Vector | AV: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}.rssand/{owner}/{repo}.atom/{owner}/{repo}/rss/branch/*and/{owner}/{repo}/atom/branch/*/{owner}/{repo}/releases.rssand/{owner}/{repo}/releases.atom/{owner}/{repo}/tags.rssand/{owner}/{repo}/tags.atom/{user}.rssand/{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 👾
Related Identifiers
Affected Products
Gitea
Red Os