Go Gitea

An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file.

In all versions of GitLab CE/EE since version 8.15, a DNS rebinding vulnerability in Gitea Importer may be exploited by an attacker to trigger Server Side Request Forgery (SSRF) attacks.

Jenkins Gitea Plugin 1.1.1 and earlier did not implement trusted revisions, allowing attackers without commit access to the Git repo to change Jenkinsfiles even if Jenkins is configured to consider them to be untrusted.

SSRF in restore-repo via unsanitized pull_request.yml Head.CloneURL

Gitea SSH Key Parser Denial of Service

Gitea versions up to and including 1.25.4 allow redirect bypasses through raw or percent-encoded backslashes in redirect_to values.

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

Repository Visibility Manipulation via Git Push Options

Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard)

Gitea versions up to and including 1.26.2 allow Git LFS object reuse to authorize private source objects for users who have repository access but lack Code-unit access.

Gitea versions from 1.5.0 before 1.26.3 have a TOTP single-use enforcement defect that allows a valid TOTP code to be accepted more than once across web two-factor authentication flows and the Basic Auth X-Gitea-OTP path.

Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.

Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo content (incomplete revocation cleanup in `DeleteCollaboration`)

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

Gitea LFS Deploy-Key Privilege Escalation

Release attachment extension allowlist bypass via web release edit form (variant of CVE-2025-68939)

Cross-Repo Information Disclosure via Org-Level Actions Run/Job APIs

The GET /api/v1/user/actions/runners/registration-token endpoint (and its owner- and repository-level equivalents) creates a new runner registration token if none exists, yet the API scope middleware classifies it as read-only because it is a GET request. A holder of a leaked…

SSRF via HTTP Redirect in Repository Migration

Gitea does not properly validate ownership when toggling OpenID URI visibility. An authenticated user may be able to change the visibility settings of other users' OpenID identities.

Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches.

Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications.

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. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to…

Denial of Service (CPU & Memory Exhaustion) via O(N^2) String Concatenation in Debian Package Upload

Gitea 1.7.2, 1.7.3 is affected by: Cross Site Scripting (XSS). The impact is: execute JavaScript in victim's browser, when the vulnerable repo page is loaded. The component is: repository's description. The attack vector is: victim must navigate to public and affected repo page.

Missing Authorization and Authorization Bypass Through User-Controlled Key and Incorrect Permission Assignment for Critical Resource and Exposure of Sensitive Information to an Unauthorized Actor in code.gitea.io/gitea

Cross-repository issue/comment attachment re-linking can expose private attachment content

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

Local File Inclusion via file:// URI in Migration Restore

GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private

Public-only API token restriction is not enforced on team API routes

Email Management API Bypasses ManageCredentials Feature Restrictions

RSS/Atom feed handlers bypass API-token scope & public-only confinement (incomplete fix of #37698)

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 version prior to version 1.5.1 contains a CWE-200 vulnerability that can result in Exposure of users private email addresses. This attack appear to be exploitable via Watch a repository to receive email notifications. Emails received contain the other recipients even if…

Private Repository Existence Disclosure via go-get Meta Endpoint

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

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

## Summary CVE-2026-20800 fixed private-info leakage to revoked users only for the notification endpoint. Two sibling endpoints that return data keyed on the caller's own relationship still do not re-check repo access at output time: - `GET /api/v1/user/starred` —…

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

Public-Only Personal access tokens scope bypass in Organization and Permission Endpoints

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

Gogs is an open source self-hosted Git service. Prior to 0.14.3, in new_form.tmpl, milestone names are rendered with Go's default auto-escaping ({{.Name}}), which converts < to < etc. This prevents direct HTML injection. However, when the browser renders the DOM, the text…

Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4.

Unbounded Arch package file metadata can cause resource amplification in Gitea package uploads

Personal access token scope enforcement bypass on the repository home page (`GET /{owner}/{repo}`) discloses private repository contents

OAuth token introspection returns metadata of tokens issued to other clients (RFC 7662 section 4 violation)