Gitea improperly exposes issue titles and repository names through previously started stopwatches
Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-20883US | — | — | ||
Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository… | ||||
02
references
External citations — patches, advisories, analysis.
- https://blog.gitea.com/release-of-1.25.4WEB
- https://github.com/go-gitea/gitea/commit/95ea2df00a70176c516b12f3cfee8c84a310280fWEB
- https://github.com/go-gitea/gitea/pull/36340WEB
- https://github.com/go-gitea/gitea/pull/36368WEB
- https://github.com/go-gitea/gitea/releases/tag/v1.25.4WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-20883ADVISORY
- https://pkg.go.dev/github.com/go-gitea/giteaPACKAGE
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