Gitea Code Injection Vulnerability

Gitea Org-mode file disclosure and code execution

Gitea WebAuthn bypass during OAuth and OIDC sign-in

Gitea fork workflow approval bypass through maintainer-triggered events

Gitea before 1.17.3 does not sanitize and escape refs in the git backend

An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which could let a malicious user gain privileges

An issue exsits in Gitea through 1.15.7, which could let a malicious user gain privileges due to client side cookies not being deleted and the session remains valid on the server…

Gitea before 1.11.2 is affected by Trusting HTTP Permission Methods on the Server Side when referencing the vulnerable admin or user API

Gitea 0.9.99 through 1.12.x before 1.12.6 does not prevent a git protocol path that specifies a TCP port number and also contains newlines (with URL encoding) in ParseRemoteAddr…

Gitea before 1.8.0 allows 1FA for user accounts that have completed 2FA enrollment

Gitea before 1.5.4 allows remote code execution because it does not properly validate session IDs

Gitea OAuth2 refresh token grant accepts access tokens

Gitea review and execution mismatch through duplicate tree entries

Gitea built-in SSH server authentication bypass through key case folding

Gitea: Cross-Repository Authorization Bypass via Release Attachment Linking Leads to Private Attachment Disclosure

Gitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)

Gitea Organization Projects Cross-Organization Authorization Bypass via Project ID (IDOR)