Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Gitea versions before 1.25.5 are affected: tracked-time entries are looked up by time ID without being limited to the issue named in the request, so deletion requests can target entries belonging to a different issue. The source does not state what privileges an attacker needs to exploit this. Upgrade to Gitea 1.25.5 or later, which contains the fix.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0039, the 33rd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:13 UTC First seen by agentprime
- 31 Oct 2026, 14:13 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-qm72-8prh-g92x
- OSV: GHSA-qm72-8prh-g92x
- nvd.nist.gov/vuln/detail/CVE-2026-25782
- github.com/go-gitea/gitea/pull/36664
- github.com/go-gitea/gitea/pull/36689
- github.com/go-gitea/gitea/commit/5ad87616c9c654fc44c611ccfd4e496257c8f96b
- github.com/go-gitea/gitea/commit/8051056075719b7629eef44689b5a61d5ff080a9
- blog.gitea.com/release-of-1.25.5
- github.com/go-gitea/gitea
- github.com/go-gitea/gitea/releases/tag/v1.25.5