CVE-2026-123006 Gitea password hash disclosure through repository search
gitea gitea: no CVSS score yet.
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.
- Published
- Modified
- Assigned by
- Gitea (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123006 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123006?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123006?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123006 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Gitea | from 28.0.0 before 28.4.0 |
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.