How many CVEs have patched oauth2LinkAccount?

2 published CVEs changed oauth2LinkAccount in go-gitea/gitea, in 2 distinct patches totalling 66 changed lines, between 2026 and 2026.

What is the latest CVE that changed oauth2LinkAccount?

CVE-2026-73535 (Gitea second-factor bypass through OpenID identity linking), published 2026-10-14, changed lines 151 to 174 of routers/web/auth/linkaccount.go.

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

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

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

oauth2LinkAccount

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

routers/web/auth/linkaccount.go

Last patched October 14, 2026

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

66

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

oauth2LinkAccount in go-gitea/gitea was changed by 2 published CVE fixes in 2026, in 2 distinct patches that added or removed 66 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 oauth2LinkAccount, newest first, with the lines each fix touched.

Gitea second-factor bypass through OpenID identity linking
CVE-2026-73535 · lines 151–174 · +8 −25 in 2 hunks
Unscored
EPSS 0.2%2026-10-14
Gitea WebAuthn bypass during OAuth and OIDC sign-in
CVE-2026-73278 · lines 151–174 · +8 −25 in 2 hunks
Critical · CVSS 9.8
EPSS 0.5%2026-10-06

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.

1completePendingLinksrouters/web/auth/linkaccount.go2 CVEs · 2 patches2026

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

How many CVEs have patched oauth2LinkAccount?: 2 published CVEs changed oauth2LinkAccount in go-gitea/gitea, in 2 distinct patches totalling 66 changed lines, between 2026 and 2026.
What is the latest CVE that changed oauth2LinkAccount?: CVE-2026-73535 (Gitea second-factor bypass through OpenID identity linking), published 2026-10-14, changed lines 151 to 174 of routers/web/auth/linkaccount.go.
How does oauth2LinkAccount compare to the rest of go-gitea/gitea?: go-gitea/gitea has 162 CVEs with a located fix in total; 2 of them changed oauth2LinkAccount.
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