Post-revocation disclosure via stale stopwatch authorization
Published Jan 22, 2026 · Updated Jan 22, 2026
Improper access control in Gitea 1.25.3 and earlier allows remote authenticated users to read private issue titles and repository names. The stopwatch API's ToStopWatches conversion returned stored entries without passing the requesting user through a current repository permission check. The user must have started a stopwatch while authorized and retain account access after repository permission is revoked; exposure is limited to the associated issue title and repository name.
Summary
What happened
Improper access control in Gitea 1.25.3 and earlier allows remote authenticated users to read private issue titles and repository names. The stopwatch API's ToStopWatches conversion returned stored entries without passing the requesting user through a current repository permission check. The user must have started a stopwatch while authorized and retain account access after repository permission is revoked; exposure is limited to the associated issue title and repository name.
The record
- CVE
- CVE-2026-20883
- Published
- Jan 22, 2026
- Updated
- Jan 22, 2026
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-284, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 22, 2026CVE publishedPublication date reported by the CVE source.
- Jan 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.25.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo