CVE-2026-129341 is an authorization vulnerability in Gitea affecting versions from 1.11.0 up to but not including 28.4.0. The flaw allowed users who uploaded attachments or release assets to delete them even after losing write access to the repository or when only having read access to issues or pull requests. The issue has been fixed in version 28.4.0 by restricting deletion to attachments uploaded by the user that are not linked to any issue, comment, or release.
A missing authorization vulnerability in Gitea allows users with read access to push branches and tags to repositories that are still being created by migration, fork, or template generation, due to the absence of server-side hooks during that window. This issue affects Gitea versions from 1.16.0 up to but not including 28.4.0. The vulnerability has been addressed in version 28.4.0, which now refuses Git over HTTP requests to repositories still in creation.
CVE-2026-128365 is an authorization vulnerability in Gitea affecting versions from 1.19.0 up to but not including 28.4.0. The flaw involves improper handling when removing a team's review request on a pull request, where a review by the built-in Actions user could be incorrectly counted as an official approval. This could allow a user with permission to change review requests to make an approval by the Actions user count toward branch protection requirements, although merging still requires explicit merge permission. The issue is fixed in version 28.4.0.
Gitea versions prior to 28.4.0 have an insufficient session expiration vulnerability when acting as an OAuth2 or OpenID Connect provider. The token endpoint did not verify the user's sign-in status, allowing refresh tokens and unused authorization codes to be exchanged for new tokens even after account deactivation or sign-in prohibition. This could allow continued access for users who should no longer be signed in. The issue is fixed in version 28.4.0, where the token endpoint refuses users who may not sign in and token introspection marks their tokens as inactive.
CVE-2026-127958 is a vulnerability in Gitea where draft pull request reviews created via the API were prematurely visible to all users who can read the pull request, including anonymous visitors of public repositories. This occurred because draft reviews were added to the pull request timeline and announced through notifications and activity feeds before being submitted. The issue was fixed in version 28.4.0 by preventing pending reviews from generating timeline entries or notifications until submission.
CVE-2026-126338 is an authorization bypass vulnerability in Gitea affecting versions from 1.14.0 up to but not including 28.4.0. It allows a signed-in user to reply to a code review comment using a review ID from a different pull request, potentially exposing diff context from repositories they cannot access. The issue is fixed in version 28.4.0 by restricting replies to only reviews of the same pull request and only allowing pending review replies from the review's author.
A vulnerability in Gitea allowed any signed-in user to query the API endpoint GET /api/v1/users/{username}/orgs/{org}/permissions and learn the role of another user within a public or limited organization, even if the membership was concealed. This exposure of sensitive information was fixed in version 28.4.0 by restricting role information to the user themselves, organization members, and site administrators.
A missing authorization check in Gitea's AGit flow allowed users with limited access (read-only code or wiki write access) to create pull requests without proper permissions. This flaw was fixed in version 28.4.0 by requiring read access to pull requests when creating them through AGit.
CVE-2026-123638 is a protection mechanism failure in Gitea affecting versions before 28.4.0. The issue arises because the 'Protected file patterns' setting was matched against git-quoted file names, causing files with special characters to bypass protection. This allowed users with write access to modify or rename protected files, potentially adding malicious workflows that execute on repository runners. The flaw is fixed in version 28.4.0 by changing the pattern matching to use unquoted file names and reporting renames with both old and new paths.
CVE-2026-123065 is a path traversal vulnerability in Gitea affecting versions from 1.15.0 up to but not including 28.4.0. It allows a user with write access to releases to delete files of attachments that do not belong to the release by submitting crafted identifiers referencing other attachments' stored files. The attachment records remain, causing download failures for the affected files. The issue is fixed in version 28.4.0 by restricting deletion to only attachments belonging to the release being edited.
CVE-2026-123009 is an improper access control vulnerability in Gitea affecting versions from 1.25.0 up to but not including 28.4.0. It allows a user who previously forked a repository and then lost access to the base repository (e.g., due to it becoming private or removal as a collaborator) to still copy branches from the base repository into their fork via the web editor and read its code. The issue was that the copy operation did not verify read permissions on the base repository. This flaw has been fixed starting with version 28.4.0, where read access is now required to copy branches from the base repository.
Gitea versions prior to 28.4.0 allowed unlimited attempts to guess six-digit TOTP passcodes during sign-in, password reset, and Basic authentication with the X-Gitea-OTP header. This flaw enabled attackers who know an account's password to bypass two-factor authentication by brute forcing the TOTP code. The issue is fixed in version 28.4.0, which now blocks further attempts for 15 minutes after five failed passcode tries.
CVE-2026-120991 is a vulnerability in Gitea where improper cleanup on a failed container blob upload could remove shared blob content used by other packages. This could cause other users' packages or image layers with identical content to become undownloadable if a package size quota is exceeded. The issue affects Gitea versions from 1.20.0 up to but not including 28.4.0. The vulnerability has been fixed in version 28.4.0 by changing the cleanup process to only remove blobs created by the failed upload.
CVE-2026-120729 is a cross-site scripting (XSS) vulnerability in Gitea affecting versions from 1.27.0 up to but not including 28.4.0. The vulnerability arises from the popup shown when hovering over an issue reference, which previously loaded data from the hovered link's path and inserted part of the response as HTML. An attacker able to post comments or other rendered content could craft a link that appears as a normal issue reference but points to a file in a repository they control, causing the popup to inject that file's content and execute script in the viewer's session. The issue has been fixed in version 28.4.0 by changing the popup to request the issue by owner, repository, and index parsed from the link, preventing arbitrary HTML/script injection.
A vulnerability in Gitea before version 28.4.0 allowed unauthenticated access to Git LFS objects for repositories that are not private when REQUIRE_SIGNIN_VIEW is enabled. This permitted anonymous clients to download LFS objects and verify their existence without authentication. The issue is fixed in version 28.4.0, where authentication is required for Git LFS endpoints if sign-in is required to view the instance.
CVE-2026-118535 is an authorization vulnerability in Gitea where a repository registered as a source of scoped workflows retained that registration after being transferred to a new owner. This allowed the new owner to modify workflows that continued to run in the previous owner's repositories with access to sensitive Actions secrets and job tokens. The issue has been fixed in version 28.4.0 by removing owner-level registrations upon transfer and ignoring registrations whose source repository no longer belongs to the registering owner.
A vulnerability in Gitea allows injection via newline characters in RubyGems package metadata, enabling an attacker who can publish a gem to forge index entries. This could mislead clients into installing attacker-chosen dependencies. The issue is fixed in version 28.3.0, and gems with such metadata are now rejected.
CVE-2026-125423 is a vulnerability in Gitea versions before 28.4.0 where a repository created with auto-init accepted pushes before initialization was complete. This allowed an attacker with repository creation permissions to push a crafted tree that followed a symbolic link, overwriting a server-side git hook. The git hook runs commands as the Gitea system user, potentially leading to privilege escalation. The issue has been fixed by ensuring the initial commit is built in a freshly initialized directory and that repositories only accept pushes once initialization is complete.
CVE-2026-119627 is a medium-severity vulnerability in Gitea affecting versions prior to 28.3.0. It allows users holding a public-only personal access token to access profile and activity feed information of limited-visibility users and organizations, which are normally hidden from anonymous visitors. The vulnerability does not allow write access and only discloses existence, profile metadata, and public activity. A fix is available in version 28.3.0.
CVE-2026-119625 is an incorrect authorization vulnerability in Gitea prior to version 28.3.0. The issue involves the `/{username}` web route accepting personal access tokens over HTTP Basic authentication without properly verifying token scopes. This allowed tokens with unrelated or limited scopes to access private user activity feeds, private organization activity, and private repositories. The vulnerability was fixed in Gitea version 28.3.0 by restricting token acceptance on this route to feeds requiring appropriate scopes such as `read:user` or `read:organization`.