CVE-2026-97626: Gitea profile feed visibility bypass via RSS/Atom Accept header

CVE-2026-97626 · Severity: info · Published 2026-10-06

Gitea, a self-hosted Git service similar to GitHub, did not properly check user permissions when serving profile activity feeds in RSS or Atom format. An attacker could request a private user or organization profile with a specially crafted HTTP header to read activity feeds and confirm the existence of restricted accounts, even when the feed feature was disabled.

Technologies: Gitea. Vendors: Gitea.

Quick answers

Is CVE-2026-97626 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-97626 being exploited in the wild.
How severe is CVE-2026-97626?
Informational severity, published 6 October 2026.
Which products and versions are affected?
Gitea before 28.1.0.
Is there a fix for CVE-2026-97626?
Yes: fixed in Gitea 28.1.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-97626 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-97626?
Check whether you run Gitea 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

  • Fixed in: Gitea 28.1.0

Technical details

The vulnerability bypasses visibility checks in the GET /{username} endpoint when Accept headers request RSS or Atom XML formats. Anonymous, restricted, and non-member users could access activity feeds of private users and organizations without authorization. The fix adds the same visibility and ENABLE_FEED setting checks that apply to standard profile pages and dedicated RSS/Atom routes.

Affected products

  • Gitea Gitea before 28.1.0

Timeline

  • 2026-10-06: disclosed
  • 2026-10-06: patched

References

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