Skip to main content
Vulnerability Database/CVE-2026-97626

CVE-2026-97626: Profile Feed Information Disclosure Flaw

CVE-2026-97626 is an information disclosure flaw affecting profile feeds that bypasses visibility checks, allowing unauthorized users to access private user and organization details. This article covers the technical details, impact assessment, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-97626 Overview

CVE-2026-97626 is an information disclosure vulnerability in Gitea, a self-hosted Git service. The flaw allows unauthenticated and unauthorized users to retrieve activity feeds from user and organization profile pages by sending an Accept: application/rss+xml or Accept: application/atom+xml header against GET /{username}. The feed response bypasses the visibility check applied to the HTML profile page and the dedicated .rss and .atom routes. The issue is tracked under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.

Critical Impact

Anonymous users, restricted users, and non-members can confirm the existence of limited or private users and private organizations, read profile details, and view public activity even when [other] ENABLE_FEED is disabled.

Affected Products

  • Gitea releases prior to v28.1.0
  • Self-hosted Gitea instances exposing user or organization profile routes
  • Gitea deployments where [other] ENABLE_FEED is set to false (the flag is bypassed)

Discovery Timeline

Technical Details for CVE-2026-97626

Vulnerability Analysis

Gitea serves user and organization profile data through multiple content negotiation paths. The HTML view at GET /{username} and the explicit .rss and .atom endpoints enforce visibility rules that respect user privacy flags, organization scope, and the [other] ENABLE_FEED configuration. When a client requests the same base path with an Accept: application/rss+xml or Accept: application/atom+xml header, Gitea returns the owner's activity feed through a code path that skips those checks. The response includes profile metadata and public activity for accounts that should be hidden from the requester.

Activity in private repositories is not exposed by this flaw. However, the leak confirms account existence and reveals public actions that administrators intended to restrict. See the GitHub Security Advisory GHSA-hf55-9cwq-2x64 for the maintainer analysis.

Root Cause

The root cause is a missing visibility check in the content-negotiation branch that generates RSS and Atom feeds from the base profile route. The handler responsible for serving feed media types does not apply the privacy filter that gates the parallel HTML and suffixed-URL handlers. The [other] ENABLE_FEED toggle also does not reach this code path.

Attack Vector

An attacker sends an HTTP GET request to a target Gitea instance against /{username} or /{orgname} and sets Accept: application/rss+xml or Accept: application/atom+xml. No authentication is required. The server returns an RSS or Atom document containing profile fields and public activity entries for limited users, private users, or private organizations. The attacker can enumerate account names and harvest activity metadata that reveals project interests, collaborators, and timing patterns.

No verified exploit code is published. The behavior can be reproduced with a standard HTTP client by overriding the Accept header on the base profile path.

Detection Methods for CVE-2026-97626

Indicators of Compromise

  • HTTP GET requests to /{username} paths carrying Accept: application/rss+xml or Accept: application/atom+xml from unauthenticated sessions
  • High-volume profile path enumeration from a single source IP targeting many {username} values
  • Responses with Content-Type: application/rss+xml or application/atom+xml returned for accounts marked limited or private

Detection Strategies

  • Parse Gitea access logs and reverse-proxy logs for the combination of base profile paths and feed Accept headers from anonymous sessions.
  • Correlate feed responses against the Gitea user table to flag requests that returned data for accounts with non-public visibility.
  • Alert on sequential requests across many usernames in short time windows, which indicates account enumeration.

Monitoring Recommendations

  • Ingest Gitea web-tier logs into a centralized log platform and retain Accept headers alongside URLs.
  • Baseline normal RSS and Atom traffic volume per source IP and flag deviations.
  • Monitor outbound responses for 200 status codes on profiles that the Gitea admin console lists as restricted.

How to Mitigate CVE-2026-97626

Immediate Actions Required

  • Upgrade Gitea to v28.1.0 or later, which contains the fixes from Pull Requests #39501 and #39507.
  • Audit access logs for anonymous feed requests against profile paths since the last upgrade window.
  • Rotate or review credentials for accounts whose activity may have been exposed to external parties.

Patch Information

The maintainers released the fix in Gitea v28.1.0. The patch adds the missing visibility check to the content-negotiation branch and honors the [other] ENABLE_FEED setting across all feed response paths. Review the GitHub Security Advisory GHSA-hf55-9cwq-2x64 for full remediation notes.

Workarounds

  • Block requests at a reverse proxy when the request path matches /{username} and the Accept header contains application/rss+xml or application/atom+xml until the upgrade is applied.
  • Restrict anonymous access to the Gitea instance through network controls or front-end authentication where feasible.
  • Require authentication for all profile and feed endpoints via proxy-level access rules.
bash
# Example NGINX rule to block feed Accept headers on base profile paths until patched
map $http_accept $gitea_feed_block {
    default                        0;
    "~*application/rss\+xml"       1;
    "~*application/atom\+xml"      1;
}

server {
    location ~ ^/[^/]+$ {
        if ($gitea_feed_block) {
            return 403;
        }
        proxy_pass http://gitea_upstream;
    }
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.