Gitea · Gitea · published 2026-11-01
CVE-2026-117649Gitea private issue disclosure through issue dependency timeline events
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-117649 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 3.5 (v3.1). Fixed upstream in Gitea 28.3.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 28.3.0.
Patch events
DevOpsGitea
Gitea security release: 28.3.0
Upgrade to
28.3.0Why: Vendor security release for server software (most severe: CVE-2026-120263).
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 | 3.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/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
0to before28.3.0(affected)
Description (from the CVE record)#
The issue timeline API and the web issue page hid cross-reference events that point at issues the reader cannot access, but not "dependency added" and "dependency removed" events. When a readable issue had been linked as a dependency to an issue in a repository the reader cannot access, for example a private repository, any reader of the first issue, including anonymous users of a public repository, received the linked issue's current title, body, state, labels, poster and attachment names through the API, and its repository, number and title on the web page. Creating the link requires access to both issues; comments and attachment downloads of the linked issue stayed protected. Dependency events are now filtered with the same read permission check; a related exposure of unlinked attachment metadata through hidden dependency placeholders was already fixed in 28.2.0.
Quoted from the CVE Program record.