Gitea leaks private issue details through issue dependency events
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Information disclosure, Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-200 and CWE-862.
Summary
Gitea before 28.3.0 does not apply read permission checks to issue dependency added and removed timeline events (CWE-862). A reader of a public issue that is linked as a dependency to an issue in a private repository receives that issue's title, body, state, labels, poster and attachment names through the API, including anonymous users of a public repository.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Gitea 28.3.0 fixes this flaw, so upgrade Gitea to 28.3.0 or later.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
- Fix · CNA Gitea (Gitea) Fixed in 28.3.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Gitea 28.3.0
20 records Highest priority Priority MEDIUM 3 MEDIUM, 17 LOW
Other records, highest priority first
- TI-2026-83610 Gitea OAuth2 auto-linking lets attackers take over accountsPriority MEDIUM 49
- TI-2026-83601 Gitea public-only token can expose private OCI blobs through package mountsPriority MEDIUM 47
- TI-2026-83594 Gitea public-only token bypass exposes private repository jobsPriority MEDIUM 47
Vendor assessments
Timeline
- 2026-11-01 Threatist record created from CVE-2026-117649
- 2026-11-04 Affected versions changed · Red Hat
- 2026-11-04 CVSS score added · Red Hat
- 2026-11-06 CVSS score added · CISA ADP
- 2026-11-06 CISA SSVC decision points changed
References
Patch 4
More Gitea vulnerabilities
- TI-2026-42785 Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation. KEVCVSS 3.1CRITICAL 9.8
- TI-2026-42033 Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts CVSS 3.1CRITICAL 9.8
- TI-2026-40842 Privilege Escalation via Access Token Scope Escalation in API CVSS 3.1CRITICAL 9.8
- TI-2026-16922 Gitea Docker image trusts spoofable reverse-proxy headers by default CVSS 3.1CRITICAL 9.8
- TI-2026-42043 Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting CVSS 3.1CRITICAL 9.1
- TI-2026-40381 OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes CVSS 3.1CRITICAL 9.1
Sources
- CVE-2026-117649 · CVE Program
- CVE-2026-117649 · NVD
- FIRST EPSS
- CVE-2026-117649 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences