Gitea: Cross-Repository Authorization Bypass via Release Attachment Linking Leads to Private Attachment Disclosure
Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-20912US | — | — | ||
Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/CVE-2026-20912WEB
- https://blog.gitea.com/release-of-1.25.4/ARTICLE
- https://bugzilla.redhat.com/show_bug.cgi?id=2432219WEB
- https://github.com/go-gitea/gitea/pull/36320FIX
- https://github.com/go-gitea/gitea/pull/36355FIX
- https://github.com/go-gitea/gitea/releases/tag/v1.25.4ARTICLE
- https://github.com/go-gitea/gitea/security/advisories/GHSA-vfmv-f93v-37mwWEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-20912WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan