Technical impact
A flaw in Gitea’s repository search endpoint caused internal commit status objects to expose the owning user’s full record, including password hash, salt, and email. Authenticated users could retrieve this sensitive data for any repository they can view that contains a commit status, resulting in a confidentiality breach that could enable credential cracking or targeted attacks.
Affected Systems
The vulnerability affects all releases of Gitea from version 28.0.0 up to, but not including, 28.4.0. The affected product is the Gitea core repository management application, and all users who have access to repositories that expose commit statuses during this period are impacted.
Risk and Exploitability
The CVSS score and EPSS metrics are not provided, and the vulnerability is not listed in the CISA KEV catalog. The attack requires a signed‑in user with visibility to the target repository; no additional privileges are necessary. Because the data exposed are critical credentials, the impact is high for the individuals whose hashes are leaked, though the exploitation is limited to the target’s repository list. Due to the lack of public exploit code reported and the requirement for authentication, the overall threat level is moderate to high, depending on the sensitivity of the exposed accounts.