Gitea · Gitea · published 2026-11-15
CVE-2026-123006Gitea password hash disclosure through repository search
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-123006 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 18% of all CVEs. This Gitea vulnerability: CVSS 6.5 (v3.1). Fixed upstream in Gitea 28.4.0, 28.3.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 28.4.0, 28.3.0.
Patch events
DevOpsGitea
Gitea security releases: 28.4.0, 28.3.0
Upgrade to
28.4.028.3.0Why: Vendor security release for server software (most severe: CVE-2026-118389).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (18th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
28.0.0to before28.4.0(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.