🛡️ CVE-2026-20800 — gitea
Description
Notification API Leaks Private Repository Issue Titles After Collaborator Permission Revocation
Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications.
Affected software
CVE-2026-20800 is recorded against 3 packages.
- code.gitea.io/gitea
- gitea
- github.com/go-gitea/gitea
Timeline and source
Published on 2 February 2026 and last revised on 3 March 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
github.com (Advisory)
nvd.nist.gov (Advisory)
blog.gitea.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| code.gitea.io/gitea | — | — |
| gitea | — | — |
| github.com/go-gitea/gitea | — | — |
References
Similar Threats
- High CVE-2021-3382
- High CVE-2020-14144
- Medium CVE-2022-38183
- Medium CVE-2022-1928
- Unknown CVE-2019-1010261
More CVE 2026 advisories
Browse all of CVE 2026 in the advisory index.
Vulnerability Monitoring
Track new vulnerabilities in gitea
CVE-2026-20800 is rated CVSS 5.0 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.