Gitea vulnerabilities

A vulnerability in Gitea LFS allows privilege escalation via deploy keys. A person with a deploy key can gain higher privileges than intended.

Private repository metadata remains accessible after access revocation. This means that information about the repository (e.g., name, description) may still be visible to users who lost permissions.

In code.gitea.io/gitea, there is missing authorization and authorization bypass through user-controlled key, incorrect permission assignment for critical resources, and exposure of sensitive information to an unauthorized actor.

The public-only API token restriction is not enforced on team API routes. This means a token intended for public access only can access team data that should be private.

The vulnerability allows bypassing the public-only scope of personal access tokens in organization and permission endpoints. This means a token intended only for public operations can access operations requiring broader privileges.

The vulnerability allows bypassing the release attachment extension allowlist via the web release edit form. This is a variant of CVE-2025-68939.

The vulnerability leaks the member list of private organizations via the /members API endpoint. This is an incomplete fix for PR #38145.

The vulnerability in OAuth token introspection returns metadata of tokens issued to other clients, violating section 4 of RFC 7662.

The vulnerability allows Local File Inclusion via file:// URI in the Migration Restore function. An attacker can read arbitrary files from the server's filesystem.

The vulnerability in the REST API exposes organization membership of private organizations to the public. Unauthorized individuals can obtain information about members of private organizations.

The vulnerability in Fork-PR Actions tasks allows reading a third private repository via the collaborative-owner branch. A missing fork-PR guard enables this.

Two Server-Side Request Forgery (SSRF) findings in Gitea 1.26.2. They allow an attacker to make requests from the server to internal resources.

The vulnerability enables cross-repository information disclosure via Org-Level Actions Run/Job APIs. An attacker can obtain data from other repositories.

The vulnerability in repository migration follows Git HTTP redirects after URL allow/block validation, enabling internal Git repository exfiltration.

The vulnerability allows re-linking attachments to issues/comments across repositories, potentially exposing private attachment content.

The vulnerability causes denial of service (CPU and memory exhaustion) via O(N^2) string concatenation during Debian package upload.

The SSH key parser in Gitea is vulnerable to denial of service, potentially leading to system overload.

OAuth2 sign-in can reactivate an administrator-deactivated account on auth sources without refresh tokens (incomplete fix of #38009).

The Email Management API bypasses ManageCredentials feature restrictions, allowing unauthorized operations on email addresses.

Null pointer dereference in the AddTime API causes authenticated denial of service.

Gitea prior to 1.27.0 contains a Server-Side Request Forgery (SSRF) vulnerability allowing authenticated attackers to bypass SSRF protections and access internal services, cloud instance metadata endpoints, or read local files such as application configuration with database credentials and signing secrets. Attackers can exploit HTTP fetch operations in migration and OAuth avatar code paths.

A vulnerability in Gitea up to version 1.26.1 allows Git smart HTTP requests authenticated with bearer tokens to bypass repository token scope checks.

A vulnerability in Gitea up to version 1.26.2 allows Git LFS object reuse, enabling users with repository access but without Code-unit access to authorize private source objects.

A stored cross-site scripting vulnerability in Gitea allows attackers to inject malicious scripts via the extensionsRequired field in glTF files rendered by the 3D file viewer. Affects versions from 1.25.0 before 1.26.0.

A vulnerability in Gitea before version 1.25.5 allows specially crafted release tag and asset names to affect dump output paths when dumping release assets.

A vulnerability in Gitea up to version 1.26.1 allows bypassing OAuth2 access token scope enforcement via HTTP Basic authentication.

A vulnerability in Gitea up to version 1.26.1 inclusive does not enforce repository-unit authorization on issue-template API endpoints. This allows unauthorized users to access sensitive data or functions related to issue templates.

Gitea versions before 1.25.5 accept malformed or injected forwarded-proto values when detecting public URLs, allowing spoofed canonical URL generation.

In Gitea 1.25.5, a branch-specific write-permission result is cached across multiple refs in one pre-receive hook session. This allows a per-branch maintainer-edit grant to be reused for other refs, escalating to full repository write access.

A vulnerability in Gitea up to version 1.26.2 allows repository RSS and Atom feed endpoints to bypass API access token scope checks, exposing private repository commit data to tokens without the required repository scope.

A vulnerability in Gitea before version 1.25.5 allows draft release data or attachments to be accessed without the required write permission.

A vulnerability in Gitea before version 1.25.5 allows a user to change another user's primary email address. The issue stems from insufficient permission validation during account modification.

Gitea versions before 1.25.5 do not enforce a timeout on git grep searches, allowing expensive searches to consume server resources.

A vulnerability in Gitea up to version 1.26.1 allows users with the 'Allow edits from maintainers' permission to commit changes to repositories they have read-only access to but should not be able to write.

In Gitea before version 1.25.5, tracked-time entries are looked up by time ID without scoping the lookup to the issue in the request URL, allowing deletion attempts to target entries from another issue.

A vulnerability in Gitea up to version 1.25.4 allows redirect bypasses by using raw or percent-encoded backslashes in the redirect_to parameter.

A vulnerability in Gitea up to version 1.26.1 causes inconsistent filtering of public-only tokens in the user organization API, leaving an incomplete fix for CVE-2025-68941.

In Gitea versions before 1.25.5, insufficient visibility checks in organization permission APIs allow disclosure of hidden members and private organizations.

In Gitea 1.26.2, unauthorized users can access labels of private organizations. This vulnerability allows information disclosure of labels that should be restricted to organization members.

In Gitea versions before 1.25.5, there is a vulnerability due to insufficient permission checks when updating or rebasing pull request branches.

A vulnerability in Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, leading to unauthorized data exposure.

A vulnerability in Gitea before version 1.26.0 allows API users to fork a repository into an organization without passing the CanCreateOrgRepo check, potentially exposing organization secrets.

Gitea versions before 1.25.5 have insufficient permission checks when listing tracked time entries. This allows users to access time data of other users without proper authorization.

A vulnerability in Gitea versions 1.5.0 through 1.26.2 allows a valid TOTP code to be reused multiple times during two-factor authentication via web flows and Basic Auth with the X-Gitea-OTP header.

A vulnerability in Gitea allows a user to delete an attachment from a repository they no longer have access to by making the request through a different accessible repository. This is due to improper verification of repository context when deleting attachments.

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

In Gitea before 1.21.2, an anonymous user can visit a private user's project. This flaw violates privacy and may lead to unauthorized access to information.

Gitea before version 1.22.2 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. This flaw may allow tracking of user activity.

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