CVE-2026-123006

Gitea password hash disclosure through repository search

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
The repository search used by the dashboard (`GET /repo/search`) returned the internal commit status object of each repository. Since 28.0.0 that object included the repository owner's full user record, so any signed-in user could read the password hash, salt and email address of the owner of any repository they can see that has a commit status. The response now contains only the state and target URL of the commit status.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Gitea to version 28.4.0 or later, which removes the password hash from commit status objects returned by the search endpoint.
  • Review repository visibility and commit status permissions to limit exposure of commit status data, ensuring only necessary users can view repository metadata.
  • Consult Gitea's release notes or support channel to confirm that your installation is up‑to‑date and that the fix has been applied, and consider disabling the /repo/search endpoint if it is not required.

Generated by OpenCVE AI on November 15, 2026 at 22:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-200
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description The repository search used by the dashboard (`GET /repo/search`) returned the internal commit status object of each repository. Since 28.0.0 that object included the repository owner's full user record, so any signed-in user could read the password hash, salt and email address of the owner of any repository they can see that has a commit status. The response now contains only the state and target URL of the commit status.
Title Gitea password hash disclosure through repository search
References
Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 15, 2026, 9:10 PM
Reserved
Nov 15, 2026, 8:29 PM
Status
Deferred
Published
Nov 15, 2026, 9:16 PM
Modified
Nov 15, 2026, 9:16 PM