apiAuth
routers/api/v1/api.go
Last patched
Overview
apiAuth in routers/api/v1/api.go (go-gitea/gitea) was changed by 2 published CVE fixes between 2025 and 2026, in 2 distinct patches that added or removed 8 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 apiAuth, newest first, with the lines each fix touched.
CVE-2025-69413 · lines 778–780 · +3 −1
Medium · CVSS 5.3EPSS 0.4%2026-01-01CVE-2025-68938 · lines 778–780 · +3 −1
Medium · CVSS 5.3EPSS 0.4%2025-12-26
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.
- 1Routesrouters/api/v1/api.go29 patches · 45 CVEs2025 to 2026
- 2reqTokenrouters/api/v1/api.go6 patches · 4 CVEs2019 to 2025
- 3checkTokenPublicOnlyrouters/api/v1/api.go5 patches · 4 CVEs2025 to 2026
- 4individualPermsCheckerrouters/api/v1/api.go4 patches · 5 CVEs2025 to 2026
- 5tokenRequiresScopesrouters/api/v1/api.go4 patches · 2 CVEs2025 to 2026
- 6repoAssignmentrouters/api/v1/api.go3 patches · 3 CVEs2026
- 7contextAuthenticatedUserrouters/api/v1/api.go2 patches · 4 CVEs2026
- 8mustNotBeArchivedrouters/api/v1/api.go2 patches · 4 CVEs2026
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 apiAuth.
- How many CVEs have patched apiAuth?
- 2 published CVEs changed apiAuth in go-gitea/gitea, in 2 distinct patches totalling 8 changed lines, between 2025 and 2026.
- What is the latest CVE that changed apiAuth?
- CVE-2025-69413 (Gitea's /api/v1/user endpoint has different responses for failed authentication depending on whether a username exists), published 2026-01-01, changed lines 778 to 780 of routers/api/v1/api.go.
- How does apiAuth compare to the rest of go-gitea/gitea?
- go-gitea/gitea has 217 CVEs with a located fix in total; 2 of them changed apiAuth.
- 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/api.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.