Advisory record · GHSA-qm72-8prh-g92x

Gitea tracked-time deletion is not scoped to the requested issue

CVSS 5.3 MediumEPSS 0.0039 · 33rd percentile

Published by the GitHub Advisory Database at 3 Jul 2026, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
code.gitea.io/giteaGo<1.25.51.25.5
Identifiers
GHSA-qm72-8prh-g92x · CVE-2026-25782 · GO-2026-6343
Weakness (CWE)
CWE-639
Published
3 Jul 2026
Updated
10 Sept 2026

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.

Written 1 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.