Gitea API disclosure of private user social graph, keys and stars

Gitea private profile information disclosure through POST request

Gitea Actions artifact v4 API unbounded request body

Gitea repository ownership escalation by administrators

Gitea private comparison disclosure with public-only tokens

Gitea required Actions check bypass through skipped workflows

Gitea Swift package manifest memory exhaustion

Gitea Alpine package parsing memory exhaustion

Gitea GitLab migration denial of service

Gitea OneDev migration denial of service

Gitea organization team policy bypass through repository API

Gitea migration memory exhaustion from zero page size

Gitea issue reference parsing CPU exhaustion

Gitea does not properly validate ownership when toggling OpenID URI visibility

Gitea's stopwatch API does not re-validate repository access permissions

Gitea's notification API does not re-validate repository access permissions when returning notification details

In Gitea through 1.17.1, repo cloning can occur in the migration function

In Gitea before 1.16.9, it was possible for users to add existing issues to projects

Gitea version 1.6.2 and earlier contains a Incorrect Access Control vulnerability in Delete/Edit file functionallity that can result in the attacker deleting files outside the…

Gitea release attachment re-linking of issue attachments

Gitea repository media API stored XSS

Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5

Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field

Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs

Gitea 1.7.0 and earlier is affected by: Cross Site Scripting (XSS)

Gitea 1.7.2, 1.7.3 is affected by: Cross Site Scripting (XSS)

Gitea private attachment disclosure through repository mismatch

Gitea local code execution through writable Git hooks

Gitea OpenID account linking without session binding

Gitea private migration creation with public-only tokens

Gitea organization repository creation token scope bypass

Gitea push-to-create bypass of FORCE_PRIVATE policy

Gitea container registry stored XSS through blob media type

In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS

Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text

Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9

Gitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations

Gitea panic on the repositories route of individual users

Gitea blind SSRF through OpenID assertion verification

Gitea hidden-owner repository listing disclosure

Gitea private reusable workflow disclosure to fork runs

Gitea OpenID discovery server-side request forgery

In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists

In Gitea before 1.21.2, an anonymous user can visit a private user's project

Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries

Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order

Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources

In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request

Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API

Gitea before 1.25.2 mishandles authorization for deletion of releases