How many CVEs have patched handleAuthorizationCode?

1 published CVEs changed handleAuthorizationCode in go-gitea/gitea, in 2 distinct patches totalling 18 changed lines, between 2026 and 2026.

What is the latest CVE that changed handleAuthorizationCode?

CVE-2026-26232 (Gitea OAuth2 authorization codes lack expiry and reuse enforcement), published 2026-07-03, changed lines 617 to 651 of routers/web/auth/oauth2_provider.go.

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

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

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

handleAuthorizationCode

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

routers/web/auth/oauth2_provider.go

Last patched July 3, 2026

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

18

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

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

Gitea OAuth2 authorization codes lack expiry and reuse enforcement
CVE-2026-26232 · lines 617–651 · +16 −2 in 2 hunks
Critical · CVSS 9.1
EPSS 0.5%2026-07-03

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

How many CVEs have patched handleAuthorizationCode?: 1 published CVEs changed handleAuthorizationCode in go-gitea/gitea, in 2 distinct patches totalling 18 changed lines, between 2026 and 2026.
What is the latest CVE that changed handleAuthorizationCode?: CVE-2026-26232 (Gitea OAuth2 authorization codes lack expiry and reuse enforcement), published 2026-07-03, changed lines 617 to 651 of routers/web/auth/oauth2_provider.go.
How does handleAuthorizationCode compare to the rest of go-gitea/gitea?: go-gitea/gitea has 162 CVEs with a located fix in total; 1 of them changed handleAuthorizationCode.
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