buildSearchIssuesRepoIDs
routers/api/v1/repo/issue.go
Last patched
Overview
buildSearchIssuesRepoIDs in routers/api/v1/repo/issue.go (go-gitea/gitea) was changed by 3 published CVE fixes in 2026, in 2 distinct patches that added or removed 9 lines in total.
go-gitea/gitea has 217 CVEs with a located fix in total, so 1% of them touched this function.
CVEs that patched it
Every published CVE whose fix changed buildSearchIssuesRepoIDs, newest first, with the lines each fix touched.
CVE-2026-24791 · lines 50–53 · +2 −1
High · CVSS 8.1EPSS 0.4%2026-08-13CVE-2026-58429 · lines 50–53 · +2 −1
Medium · CVSS 4.9EPSS 0.5%2026-08-13CVE-2026-25714 · lines 50–53 · +2 −1
Medium · CVSS 4.3EPSS 0.4%2026-07-03
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.
- 1DeleteIssuerouters/api/v1/repo/issue.go6 patches · 8 CVEs2026
- 2EditIssuerouters/api/v1/repo/issue.go6 patches · 8 CVEs2026
- 3ListIssuesrouters/api/v1/repo/issue.go4 patches · 1 CVE2026
- 4getRepoIssueByIndexForDoerrouters/api/v1/repo/issue.go4 patches · 1 CVE2026
- 5GetIssuerouters/api/v1/repo/issue.go4 patches · 1 CVE2026
- 6UpdateIssueDeadlinerouters/api/v1/repo/issue.go4 patches · 1 CVE2026
- 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 buildSearchIssuesRepoIDs.
- How many CVEs have patched buildSearchIssuesRepoIDs?
- 3 published CVEs changed buildSearchIssuesRepoIDs in go-gitea/gitea, in 2 distinct patches totalling 9 changed lines, between 2026 and 2026.
- What is the latest CVE that changed buildSearchIssuesRepoIDs?
- CVE-2026-24791 (Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes), published 2026-08-13, changed lines 50 to 53 of routers/api/v1/repo/issue.go.
- How does buildSearchIssuesRepoIDs compare to the rest of go-gitea/gitea?
- go-gitea/gitea has 217 CVEs with a located fix in total; 3 of them changed buildSearchIssuesRepoIDs.
- 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.