Gitea: Cross-Repository Authorization Bypass via Release Attachment Linking Leads to Private Attachment Disclosure
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.1epss 0.4%
exploitation probability
0.4%top 66% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
Gitea · Gitea Open Source Git ServerReferences
https://access.redhat.com/security/cve/CVE-2026-20912https://blog.gitea.com/release-of-1.25.4/https://bugzilla.redhat.com/show_bug.cgi?id=2432219https://github.com/go-gitea/gitea/pull/36320https://github.com/go-gitea/gitea/pull/36355https://github.com/go-gitea/gitea/releases/tag/v1.25.4https://github.com/go-gitea/gitea/security/advisories/GHSA-vfmv-f93v-37mwhttps://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-20912.json