Gitea's RSS/Atom feed handlers accept API tokens via Basic authentication but fail to enforce token scope or public-only confinement checks that are applied to other download handlers. This incomplete fix of a prior issue (#37698) results in private repository content being accessible through feed routes even when tokens are restricted to public-only or lack repository read scope. The affected feed routes include repository home feeds, branch feeds, release feeds, tag feeds, and user activity feeds. The vulnerability allows tokens that should be confined to public data or limited scopes to retrieve private commit SHAs, messages, author emails, private release names and notes, private tag names and messages, and private user activity streams. The issue was verified against Gitea 1.26.2 and affects all versions before 1.27.0.

Tokens that are intended to be confined to public data or limited scopes can access private repository content via RSS/Atom feed endpoints. This leads to unauthorized disclosure of private commit information, release details, tags, and user activity streams. The vulnerability does not allow cross-user access; the requesting user must have repository read permissions. However, it breaks the confinement guarantees of personal access tokens, potentially exposing sensitive data to third-party services, CI integrations, or attackers who obtain such tokens.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch links are provided, users should monitor Gitea advisories for updates addressing this token scope enforcement gap in feed handlers. Until a fix is available, avoid using public-only or limited-scope tokens with feed endpoints, and restrict token usage to trusted environments. Review token scopes and consider revoking tokens that may be exposed to lower-trust integrations.