Gitea up to 28.0.0 Feed Visibility username information disclosure

Summaryinfo

A vulnerability was found in Gitea up to 28.0.0. It has been declared as problematic. This affects an unknown part of the component Feed Visibility. Such manipulation of the argument Username leads to information disclosure. This vulnerability is uniquely identified as CVE-2026-97626. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Gitea up to 28.0.0. Affected by this issue is some unknown processing of the component Feed Visibility. The manipulation of the argument username with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:

Requesting a user or organization profile page (`GET /{username}`) with an `Accept: application/rss+xml` or `Accept: application/atom+xml` header returned the owner's activity feed without the visibility check that the profile page and the `.rss` and `.atom` routes apply. Anonymous users, restricted users and non-members could confirm the existence of limited or private users and private organizations and read their profile details and public activity, also when `[other] ENABLE_FEED` was disabled. Activity in private repositories was not included.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-97626 since 10/05/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/07/2026). The MITRE ATT&CK project declares the attack technique as T1592.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Gitea

Version

• 28.0

License

• open-source

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion