getRepoIssueByIndexForDoer
routers/api/v1/repo/issue.go
Last patched
Overview
getRepoIssueByIndexForDoer in routers/api/v1/repo/issue.go (go-gitea/gitea) was changed by 1 published CVE fix in 2026, in 4 distinct patches that added or removed 14 lines in total.
go-gitea/gitea has 217 CVEs with a located fix in total, so 0% of them touched this function.
CVEs that patched it
Every published CVE whose fix changed getRepoIssueByIndexForDoer, newest first, with the lines each fix touched.
CVE-2026-129525 · lines 996–1009 · +14 −0
Medium · CVSS 5.4EPSS 0.2%2026-11-15
Get an alert when the next CVE fix lands in go-gitea/gitea, with the patched functions.
Monitor these CVEsOther functions in these files
Functions in the same file that CVE fixes also changed.
- 1EditIssuerouters/api/v1/repo/issue.go6 patches · 8 CVEs2026
- 2DeleteIssuerouters/api/v1/repo/issue.go6 patches · 8 CVEs2026
- 3GetIssuerouters/api/v1/repo/issue.go4 patches · 1 CVE2026
- 4ListIssuesrouters/api/v1/repo/issue.go4 patches · 1 CVE2026
- 5UpdateIssueDeadlinerouters/api/v1/repo/issue.go4 patches · 1 CVE2026
- 6buildSearchIssuesRepoIDsrouters/api/v1/repo/issue.go2 patches · 3 CVEs2026
- 7SearchIssuesrouters/api/v1/repo/issue.go2 patches · 1 CVE2025
Other hotspots in the repository
Functions in go-gitea/gitea changed by the most distinct patches.
Frequently asked questions
Common questions about CVE fixes to getRepoIssueByIndexForDoer.
- How many CVEs have patched getRepoIssueByIndexForDoer?
- 1 published CVEs changed getRepoIssueByIndexForDoer in go-gitea/gitea, in 4 distinct patches totalling 14 changed lines, between 2026 and 2026.
- What is the latest CVE that changed getRepoIssueByIndexForDoer?
- CVE-2026-129525 (Gitea pull request disclosure to members with access to issues only), published 2026-11-15, changed lines 996 to 1009 of routers/api/v1/repo/issue.go.
- How does getRepoIssueByIndexForDoer compare to the rest of go-gitea/gitea?
- go-gitea/gitea has 217 CVEs with a located fix in total; 1 of them changed getRepoIssueByIndexForDoer.
- What do the line numbers refer to?
- Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.
References
- routers/api/v1/repo/issue.go on GitHub (opens in a new tab)
- All patched functions in go-gitea/gitea
- Patched functions directory
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Track go-gitea/gitea CVEs
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.