CVE-2026-123006: Gitea password hash disclosure through repository search
Affects GiteaSource CVE Database V5
Not known to be exploited : upgrade to 28.4.0 soon.
Data as of 15 Nov 2026, 21:19 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 28.4.0
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Gitea to 28.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Giteagitea.dev | Affected
| Fixed in
|
AI-suggested
Upgrade Gitea to version 28.4.0 or later, where the vulnerability is fixed by removing sensitive user data from the repository search response. No other mitigation is required as the fix is official and complete.
Description
A vulnerability in Gitea versions 28.0.0 through 28.3.x allowed signed-in users to retrieve sensitive information including password hashes, salts, and email addresses of repository owners via the repository search endpoint. This issue was fixed in version 28.4.0 by limiting the commit status response to only include the state and target URL.
References
- github.com/go-gitea/gitea/security/advisories/GHSA-frjx-8pcw-8c9q (opens in a new tab)
- github.com/go-gitea/gitea/pull/40377 (opens in a new tab)
- github.com/go-gitea/gitea/pull/40384 (opens in a new tab)
- blog.gitea.com/release-of-28.4.0/ (opens in a new tab)
- github.com/go-gitea/gitea/releases/tag/v28.4.0 (opens in a new tab)