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

Advisory record · `GHSA-qm72-8prh-g92x`

- **Identifiers:** `GHSA-qm72-8prh-g92x` · `CVE-2026-25782` · `GO-2026-6343`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-639](https://cwe.mitre.org/data/definitions/639.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 3 Jul 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `code.gitea.io/gitea` (Go): affected `<1.25.5`; fixed in `1.25.5`

## 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

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`, from 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](https://osv.dev/vulnerability/GHSA-qm72-8prh-g92x)

## Sources

- [GitHub Advisory Database: GHSA-qm72-8prh-g92x](https://github.com/advisories/GHSA-qm72-8prh-g92x)
- [OSV: GHSA-qm72-8prh-g92x](https://osv.dev/vulnerability/GHSA-qm72-8prh-g92x)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-25782>
- <https://github.com/go-gitea/gitea/pull/36664>
- <https://github.com/go-gitea/gitea/pull/36689>
- <https://github.com/go-gitea/gitea/commit/5ad87616c9c654fc44c611ccfd4e496257c8f96b>
- <https://github.com/go-gitea/gitea/commit/8051056075719b7629eef44689b5a61d5ff080a9>
- <https://blog.gitea.com/release-of-1.25.5>
- <https://github.com/go-gitea/gitea>
- <https://github.com/go-gitea/gitea/releases/tag/v1.25.5>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qm72-8prh-g92x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qm72-8prh-g92x/>. Everything for agents: <https://agentprime.io/llms.txt>.
