Gitea private issue disclosure through issue dependency timeline events
Only Gitea 28.2.0 and earlier are affected, and only where a readable issue is linked as a dependency of an issue in a repository the reader cannot access. Fixed in 28.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 28.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Gitea, the self-hosted Git service, is affected: its issue timeline API and web issue page could expose details of private issues to anyone who could read a linked public issue. The exposed details included the private issue's title, body, state, labels, poster, and attachment names, and the impact is that confidential information in private repositories could be seen by unauthorized users, including anonymous visitors.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
Affected versions are Gitea 28.2.0 and earlier A readable issue is linked as a dependency to an issue in a repository the reader cannot accessUpgrade to a fixed version: 28.3.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- gitea.dev
fixed in 28.3.0
Evidence 7
- Advisory
- Patch
- Patch
- Patch
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-117649
What does this mean?
Issue dependency timeline events can reveal a private issue to a reader who cannot access the repository that holds it. The advisory calls this private issue disclosure.Source: github.com
Am I affected, and how do I check?
Gitea 28.2.0 and earlier are affected. The affected setup involves a readable issue being linked as a dependency to an issue in a repository the reader cannot access. To check the installed version, run gitea --version on the server or look at the version shown in the site administration page.Source: github.com
What should I do about it?
Upgrade Gitea to 28.3.0 or later, which contains the fix. The sources provided do not describe a workaround.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data