CVE-2026-119441 is an authorization vulnerability in Gitea affecting versions from 1.27.0 up to but not including 28.3.0. The DELETE API endpoint for deleting all repositories of an organization did not properly enforce restrictions on public-only access tokens, allowing such tokens to delete private repositories of a public organization. This flaw has been fixed in version 28.3.0.
CVE-2026-118504 is a vulnerability in Gitea where the REST API allowed modifications to issues on archived repositories, bypassing the web interface's restrictions. This flaw permitted users with issue modification permissions to edit, close, delete issues, and alter related metadata on archived repositories, which are intended to be immutable. The issue was partially fixed in Gitea 28.2.0 and fully addressed in 28.3.0.
CVE-2026-118395 is a vulnerability in Gitea versions before 28.3.0 where personal access tokens restricted to public resources ('public-only') could bypass intended restrictions and create private repositories and organizations. Specifically, while some API endpoints correctly prevented public-only tokens from creating repositories, others still allowed such tokens with write scopes to create private repositories in organizations, create private organizations, and generate private repositories from templates. The tokens could not read the private repositories they created. This issue was fixed in Gitea version 28.3.0.
CVE-2026-118394 is a vulnerability in Gitea affecting versions from 1.23.0 up to but not including 28.3.0. It involves the OAuth2 userinfo endpoint improperly exposing private organization and team membership information of token owners when certain public-only OAuth2 tokens or personal access tokens are used. No repository content is disclosed. The issue is fixed in version 28.3.0.
CVE-2026-117685 is a critical authorization vulnerability in Gitea's OCI registry cross-repository blob mount functionality. It allows a public-only token with write:package scope to mount a blob from a private package into a public package, enabling unauthorized download of private container layers through the public package.
CVE-2026-117677 is a vulnerability in Gitea versions prior to 28.3.0 where the application improperly handles uploaded Helm chart archives. The decompression process reads all tar entries without limiting the decompressed size and does so before enforcing package size quotas based on compressed size. This allows a user with package write access to upload small, highly compressed archives that cause excessive CPU consumption, degrading service availability. The flaw does not permit code execution or unauthorized data access.
A vulnerability in Gitea before version 28.3.0 allowed personal access tokens restricted to public resources to list private repositories on user profiles and organization pages. This flaw exposed repository names and metadata but did not disclose repository content. The issue affected the repositories, stars, and watching tabs of user profiles and the repository list of organization home pages. The API and profile activity tab were not affected as they already enforced the restriction.
CVE-2026-116474 is a vulnerability in Gitea affecting versions from 1.19.0 up to but not including 28.3.0. It allows a Gitea Actions job authenticated as the system user 'gitea-actions' to register an email address and GPG key without required email confirmation, causing the email to be stored as activated. This leads to commit signatures made with the user's own key being displayed as trusted and signed by the instance in all repositories where they appear, including those the user cannot write to. The impact is limited to the displayed signature status; no access escalation or bypass of enforcement mechanisms occurs. The issue is fixed in version 28.3.0 where the API now rejects system users.
CVE-2026-116296 is a missing authorization vulnerability in Gitea affecting API routes for releases, release assets, milestones, and repository labels on archived repositories. Users with write access or tokens scoped to write on archived repositories could modify or delete release assets, releases, tags, milestones, and labels despite the repository being intended as read-only. This issue is fixed in Gitea version 28.3.0, where such modification requests now return a 423 Locked status for archived repositories.
CVE-2026-116289 is a critical authorization vulnerability in Gitea affecting versions prior to 28.3.0. It allows an attacker holding a personal access token restricted to public resources but with write:organization scope to register an organization-level Actions runner. This runner can access private repositories' workflows, secrets, variables, and task tokens, exposing sensitive information. The vulnerability expands the reach of restricted tokens beyond their intended scope but does not grant more privileges than the owner's full account already has. A fix is available in Gitea version 28.3.0.
CVE-2026-113429 is a cross-site scripting (XSS) vulnerability in Gitea affecting versions prior to 28.3.0. It arises from legacy Actions artifact uploads (v1 to v3) that stored the Content-Encoding header unchecked and served it as the artifact's Content-Type on download. If the Content-Type starts with 'video/' or 'audio/', it disables the sandboxing Content-Security-Policy, allowing an attacker who can run an Actions job to upload an artifact that a browser renders as HTML on the Gitea origin. This can lead to script execution in the context of the victim's session, potentially allowing an administrator to gain control of the instance. The issue is fixed in version 28.3.0 by restricting stored headers and serve headers to valid media types only.
CVE-2026-120263 is a critical improper authentication vulnerability in Gitea versions prior to 28.3.0. When the oauth2_client ACCOUNT_LINKING setting is set to auto and registration is enabled, the account linking process incorrectly allowed an attacker to link their OAuth2 identity to another user's Gitea account by submitting that user's username or email. This flaw could let an attacker sign in as the victim without a password, including administrator accounts. The issue is fixed in Gitea 28.3.0 by requiring that automatic linking only occurs when the existing account matches the OAuth2 provider's email or username; otherwise, the account password is required.
CVE-2026-118386 is an incorrect authorization vulnerability in Gitea affecting versions from 1.19.0 up to but not including 28.3.0. It allows a user with read access to a repository to trigger workflows on commits they control without proper approval, potentially exposing repository secrets and a write-access token. The issue arises because workflows triggered by pull request reviews were executed based on the commit named in the review without verifying that the commit belonged to the reviewed pull request. This flaw has been fixed in version 28.3.0.
A cross-site request forgery (CSRF) vulnerability in Gitea versions up to 28.1.0 allows a repository administrator to have the topics of their repository changed by visiting a malicious page. The affected endpoint lacks proper sign-in middleware, enabling unauthorized cross-origin requests. No other repository settings are affected through this route.
Gitea Notification API in versions prior to 1.26.4 leaks private issue and pull request metadata through the 'subject' field of notification threads after a user's access to a private repository has been revoked. While the 'repository' field is correctly nulled, the 'subject' field still exposes sensitive information such as issue titles, URLs, state, and comment activity. This allows users who lost access to continue observing ongoing activity on private issues or pull requests via notifications.
Gitea Actions Artifacts V4 signed URLs suffer from an HMAC signature ambiguity that allows an attacker with permission to run a Gitea Actions job to rewrite signed URLs. This enables unauthorized reading of artifacts from other repository tasks and unauthorized writing to other task artifact upload staging areas, including private repositories. The vulnerability arises because the HMAC input concatenates multiple fields without delimiters, allowing different URL parameter combinations to produce the same signature. This flaw affects versions from 1.22.0 up to but not including 1.26.2.
Gitea Actions contains a vulnerability in the fork pull request workflow approval gate that allows an attacker with a single unprivileged account and one-time maintainer approval on a benign fork PR to permanently bypass approval for all future fork PR workflow runs from that user on the same repository. This bypass occurs because the approval check only verifies if the user has any previously approved run in the repository, without considering the pull request, commit, or workflow contents. The vulnerability affects all Gitea versions from v1.20.0 onward and remains unpatched as of this disclosure.
A vulnerability in Gitea's SSH LFS sub-verb handling allows any authenticated SSH user to bypass access controls and obtain valid LFS credentials for private repositories they do not have permission to access. This flaw enables unauthorized read access to all LFS objects in any private repository on the instance. The issue arises because unknown LFS sub-verbs cause the permission check to incorrectly grant access. This affects Gitea versions from 1.23.0 up to but not including 1.26.3. No official patch or fix has been confirmed yet.
Gitea 1.25.4 and earlier versions prior to 1.26.4 contain a server-side request forgery (SSRF) vulnerability in the repository migration endpoint. The vulnerability arises because Gitea validates the initial migration URL to block internal addresses but does not re-validate URLs after following HTTP 302 redirects. This allows a low-privilege user to cause Gitea to access internal services by redirecting from an attacker-controlled server to internal IP addresses, effectively using Gitea as a proxy to access otherwise inaccessible internal resources.