SearchRepositoryCondition
models/repo/repo_list.go
Last patched
Overview
SearchRepositoryCondition in models/repo/repo_list.go (go-gitea/gitea) was changed by 4 published CVE fixes in 2026, in 2 distinct patches that added or removed 12 lines in total.
go-gitea/gitea has 217 CVEs with a located fix in total, so 2% of them touched this function.
CVEs that patched it
Every published CVE whose fix changed SearchRepositoryCondition, newest first, with the lines each fix touched.
CVE-2026-119627 · line 376 · +1 −2
Medium · CVSS 4.3EPSS 0.3%2026-11-01CVE-2026-119625 · line 376 · +1 −2
Medium · CVSS 4.3EPSS 0.2%2026-11-01CVE-2026-116474 · line 376 · +1 −2
Medium · CVSS 6.5EPSS 0.2%2026-11-01CVE-2026-112887 · line 376 · +1 −2
Medium · CVSS 4.3EPSS 0.3%2026-11-01
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.
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 SearchRepositoryCondition.
- How many CVEs have patched SearchRepositoryCondition?
- 4 published CVEs changed SearchRepositoryCondition in go-gitea/gitea, in 2 distinct patches totalling 12 changed lines, between 2026 and 2026.
- What is the latest CVE that changed SearchRepositoryCondition?
- CVE-2026-119627 (Gitea limited-visibility profile disclosure with public-only tokens), published 2026-11-01, changed lines 376 of models/repo/repo_list.go.
- How does SearchRepositoryCondition compare to the rest of go-gitea/gitea?
- go-gitea/gitea has 217 CVEs with a located fix in total; 4 of them changed SearchRepositoryCondition.
- 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
- models/repo/repo_list.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.