How many CVEs have patched canChangeRepoTeam?

5 published CVEs changed canChangeRepoTeam in go-gitea/gitea, in 1 distinct patches totalling 65 changed lines, between 2026 and 2026.

What is the latest CVE that changed canChangeRepoTeam?

CVE-2026-73126 (Gitea private workflow badge token scope bypass), published 2026-10-14, changed lines 227 to 239 of routers/api/v1/repo/teams.go.

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

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

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

canChangeRepoTeam

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

routers/api/v1/repo/teams.go

Last patched October 14, 2026

5

CVEs

That changed this function

1

Distinct patches

Backports counted once

65

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

canChangeRepoTeam in go-gitea/gitea was changed by 5 published CVE fixes in 2026, in 1 distinct patches that added or removed 65 lines in total.

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

CVEs that patched it

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

Gitea private workflow badge token scope bypass
CVE-2026-73126 · lines 227–239 · +13 −0
Medium · CVSS 4.3
EPSS 0.3%2026-10-14
Gitea organization listing token scope bypass
CVE-2026-70407 · lines 227–239 · +13 −0
Medium · CVSS 4.3
EPSS 0.3%2026-10-14
Gitea restricted-user organization metadata disclosure
CVE-2026-66853 · lines 227–239 · +13 −0
Medium · CVSS 4.3
EPSS 0.4%2026-10-14
Gitea restricted-user package visibility bypass
CVE-2026-66849 · lines 227–239 · +13 −0
Medium · CVSS 4.3
EPSS 0.4%2026-10-14
Gitea organization team policy bypass through repository API
CVE-2026-60010 · lines 227–239 · +13 −0
Medium · CVSS 6.5
EPSS 0.5%2026-10-14

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 canChangeRepoTeam.

How many CVEs have patched canChangeRepoTeam?: 5 published CVEs changed canChangeRepoTeam in go-gitea/gitea, in 1 distinct patches totalling 65 changed lines, between 2026 and 2026.
What is the latest CVE that changed canChangeRepoTeam?: CVE-2026-73126 (Gitea private workflow badge token scope bypass), published 2026-10-14, changed lines 227 to 239 of routers/api/v1/repo/teams.go.
How does canChangeRepoTeam compare to the rest of go-gitea/gitea?: go-gitea/gitea has 162 CVEs with a located fix in total; 5 of them changed canChangeRepoTeam.
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