How many CVEs have patched tokenRequiresScopes?

2 published CVEs changed tokenRequiresScopes in go-gitea/gitea, in 2 distinct patches totalling 30 changed lines, between 2025 and 2026.

What is the latest CVE that changed tokenRequiresScopes?

CVE-2026-73804 (Gitea API token scope escalation through HTTP signatures), published 2026-10-14, changed lines 333 of routers/api/v1/api.go.

How does tokenRequiresScopes compare to the rest of go-gitea/gitea?

go-gitea/gitea has 162 CVEs with a located fix in total; 2 of them changed tokenRequiresScopes.

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.

RadicalNotion.AI

Log in Create an account

go-gitea/gitea

Function

tokenRequiresScopes

Name: tokenRequiresScopes in go-gitea/gitea: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

routers/api/v1/api.go

Last patched October 14, 2026

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

30

Lines changed

Added plus removed

2025–2026

Years

By CVE publication date

Overview

tokenRequiresScopes in go-gitea/gitea was changed by 2 published CVE fixes between 2025 and 2026, in 2 distinct patches that added or removed 30 lines in total.

go-gitea/gitea has 162 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed tokenRequiresScopes, newest first, with the lines each fix touched.

Gitea API token scope escalation through HTTP signatures
CVE-2026-73804 · line 333 · +1 −1
Unscored
EPSS 0.2%2026-10-14
Gitea mishandles access to a private resource upon receiving an API token with scope limited to public resources
CVE-2025-68941 · lines 309–338 · +12 −16 in 2 hunks
Medium · CVSS 5.3
EPSS 0.3%2025-12-26

Get an alert when the next CVE fix lands in go-gitea/gitea, with the patched functions.

Monitor gitea CVEs

Other 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 CVE fixes.

Routes22 CVEs · routers/api/v1/api.go hookPostReceiveUpdateRepoByOptions10 CVEs · routers/private/hook_post_receive.go Clone9 CVEs · modules/git/repo.go attachmentBelongsToRepoOrIssue9 CVEs · routers/api/v1/repo/issue_attachment.go Close9 CVEs · routers/api/v1/repo/file.go GetRawFileOrLFS9 CVEs · routers/api/v1/repo/file.go

All patched functions in go-gitea/gitea

Frequently asked questions

Common questions about CVE fixes to tokenRequiresScopes.

How many CVEs have patched tokenRequiresScopes?: 2 published CVEs changed tokenRequiresScopes in go-gitea/gitea, in 2 distinct patches totalling 30 changed lines, between 2025 and 2026.
What is the latest CVE that changed tokenRequiresScopes?: CVE-2026-73804 (Gitea API token scope escalation through HTTP signatures), published 2026-10-14, changed lines 333 of routers/api/v1/api.go.
How does tokenRequiresScopes compare to the rest of go-gitea/gitea?: go-gitea/gitea has 162 CVEs with a located fix in total; 2 of them changed tokenRequiresScopes.
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

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.

Create an account See pricing