CVE-2026-50105: Gitea authorization bypass in RSS and Atom feed handlers

CVE-2026-50105 · Severity: medium · CVSS 4.3 · Published 2026-07-21

Gitea is an open-source self-hosted software development platform. A vulnerability in its RSS and Atom feed handlers allows users with restricted access tokens to view private repository information that should be hidden from them. While this does not allow unauthorized users to access the platform, it means that limited-privilege tokens (such as those given to third-party tools) can leak private commit messages, release notes, and activity streams.

Technologies: Gitea, code.gitea.io/gitea (Go), gitea.dev (Go). Vendors: Gitea, Go.

Quick answers

Is CVE-2026-50105 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-50105 being exploited in the wild.
How severe is CVE-2026-50105?
Medium severity, with a CVSS score of 4.3, published 21 July 2026.
Which products and versions are affected?
Gitea < 1.27.0; code.gitea.io/gitea (Go) < 1.27.0, SEMVER:introduced=0,fixed=1.27.0; gitea.dev (Go) SEMVER:introduced=0,fixed=1.27.0.
Is there a fix for CVE-2026-50105?
Yes. code.gitea.io/gitea (Go): upgrade to 1.27.0 or later; gitea.dev (Go): upgrade to 1.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50105 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-50105?
Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • code.gitea.io/gitea (Go): upgrade to 1.27.0 or later
    go get code.gitea.io/gitea@v1.27.0
  • gitea.dev (Go): upgrade to 1.27.0 or later
    go get gitea.dev@v1.27.0

Technical details

Gitea's RSS/Atom feed handlers (including repo home, branch, release, and tag feeds) accept API tokens via Basic authentication but fail to call scope enforcement checks like 'CheckTokenScopes' or 'CheckRepoScopedToken'. This results in two confinement bypasses: tokens marked as 'public-only' can still access private repository feeds, and tokens with restricted scope categories (e.g., 'read:issue' only) can access repository commit and release metadata. The vulnerability allows the disclosure of commit SHAs, messages, author details, and release notes, though it does not expose raw file blobs. This issue is an incomplete fix of a previous security hardening effort that addressed similar leaks in download handlers. The vulnerability is patched in version 1.27.0.

Affected products

  • Gitea Gitea < 1.27.0

Identifiers

  • CVE-2026-50105
  • GHSA-6cqf-375w-639g
  • GO-2026-6036

Timeline

  • 2026-07-13: disclosed
  • 2026-07-21: advisory
  • 2026-07-21: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.