CVE-2026-129525

Gitea pull request disclosure to members with access to issues only

Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. A user who can read a repository's issues but not its pull requests could read pull request data through the issue sub-resources of the API (timeline, attachments, labels, subscriptions, tracked times and reactions), and list pull requests through the repository's issue search and milestone pages; the same applied in the other direction. These endpoints now check read access to the unit the item belongs to. The API endpoints were fixed in 28.2.0 and 28.3.0, the search and milestone pages in 28.4.0.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-129341

Gitea release asset deletion by former writers

The web endpoint that removes an attachment skipped the permission check when the request came from the user who had uploaded the attachment, and it was reachable with read access to issues or pull requests. A user who had uploaded a release asset could still delete it after losing write access to the repository. The endpoint now only deletes attachments that the user uploaded and that are not yet linked to an issue, comment or release.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-129337

Gitea push without write access to repositories still being created

Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforce write access. A repository that is still being created by a migration, fork or template generation has no hooks yet, so a user with read access to it could push branches and tags during that window, or after a failed migration that left the repository in that state. Git over HTTP now refuses requests to repositories that are still being created.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-128365

Gitea required approval bypass through team review request removal

Removing a team's review request looked up a review by the negated team ID, which for the team with ID 2 is the ID of the built-in Actions user, and marked the review it found as official. In the organization that owns that team, a user who can change the review requests of a pull request could make an approval left by the Actions user count toward the approvals required by branch protection. Merging still required permission to merge. Removing a team review request no longer changes any review.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-128359

Gitea OAuth2 provider tokens issued to disabled users

When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged for new tokens, so applications that sign users in through Gitea kept them signed in. The token endpoint now refuses users who may not sign in, and token introspection reports their tokens as inactive.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-127958

Gitea disclosure of pending pull request reviews created through the API

A pull request review created through the API as a draft (`event` set to `PENDING` or left empty) was added to the pull request timeline and announced through notifications and activity feeds like a submitted review. Its body and line comments were therefore visible to everyone who can read the pull request, including anonymous visitors of a public repository, before the reviewer submitted it. Pending reviews no longer get a timeline entry or notifications until they are submitted.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-126338

Gitea private diff disclosure through code comment replies

Replying to a code review comment accepted a review ID that belongs to a different pull request, through the web form, the API and incoming mail replies. A signed-in user could reply on a pull request they can access with the ID of a review in a repository they cannot read, and the new comment was attached to that review and received the diff context of the commented lines. Replies are now only accepted for a review of the same pull request, and for a pending review only from its author.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-125617

Gitea hidden organization membership disclosure through the permissions API

`GET /api/v1/users/{username}/orgs/{org}/permissions` only checked that the organization is visible to the caller and then returned the named user's role in it. Any signed-in user could learn whether another user is an owner, admin or member of a public or limited organization, including for members who conceal their membership. The roles are now only returned to the user themselves, to members of the organization and to site administrators.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-123642

Gitea pull request creation without pull request access through AGit

The AGit flow (pushing to `refs/for/...`) did not check the pusher's access to pull requests again when it created the pull request. A user or deploy key with read access to the code only, or with write access to the wiki over SSH, could open pull requests in a repository where they have no access to pull requests. Creating a pull request through AGit now requires read access to the pull requests of the repository and is refused for wiki pushes.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-123638

Gitea protected file pattern bypass with quoted file names

The "Protected file patterns" setting of a branch protection rule was checked against file names as git prints them, and git quotes names that contain a double quote, a backslash or a control character. Such names never matched a pattern, so a user with write access could add or change files under a protected pattern by direct push or through a pull request merge, and could move a protected file out of the pattern's reach by renaming it. Where the patterns protect workflow files, this allowed adding a workflow that then ran on the repository's runners. Changed files are now listed unquoted, and a rename reports both the old and the new path.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-123065

Gitea deletion of arbitrary attachment files through release edit

When a release was edited, the files of the attachments to remove were deleted by the identifiers submitted in the form rather than by the attachments verified to belong to the release. A user with write access to the releases of any repository, including their own, could submit a crafted identifier that resolves to the stored file of another attachment and delete it, provided they know that attachment's UUID. The attachment record stayed, so downloads of the affected issue, comment or release file failed. Release edits now only delete the files of attachments that belong to the release.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-123009

Gitea base repository code disclosure through the web editor in forks

When a file is edited in a fork through the web editor, Gitea can first copy a branch from the base repository into the fork. That copy did not check whether the user may read the base repository's code. A user who had forked a repository and later lost access to it, for example after it was made private or they were removed as a collaborator, could keep copying its current branches into their fork and read them. The copy now requires read access to the code of the base repository.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-123002

Gitea missing attempt limit for TOTP passcodes

Gitea accepted an unlimited number of wrong TOTP passcodes during sign-in, in the password reset flow and for Basic authentication with the `X-Gitea-OTP` header. An attacker who already knows an account's password could guess the six-digit passcode by trying codes at a high rate and sign in despite two-factor authentication. After five failed passcodes, further attempts for the account are now refused for 15 minutes.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-120991

Gitea deletion of shared container blobs on rejected uploads

When a container blob upload was rejected, for example because it exceeded a package size quota, the cleanup removed the blob from storage even if the same content already existed and was used by other packages. On an instance with a package quota configured, a user who can upload container images and has the exact content of another owner's package file or image layer could make it undownloadable. The cleanup now only removes blobs that the failed upload created.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-120729

Gitea stored cross-site scripting in the issue reference popup

The popup shown when hovering an issue reference loaded its data from the path of the hovered link and inserted part of the response as HTML. A user who can post a comment or other rendered content could add a link that is displayed as an ordinary issue reference but points to a file in a repository they control, so that the popup inserted that file's content into the page of anyone hovering the link and ran script in the viewer's session. The popup now requests the issue by the owner, repository and index parsed from the link.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-120725

Gitea anonymous Git LFS access despite required sign-in

With `REQUIRE_SIGNIN_VIEW = true`, the Git LFS endpoints still answered unauthenticated requests for repositories that are not private. An anonymous client who knows the path of such a repository and the SHA-256 of an LFS object could download the object, and could use the batch endpoint to test whether an object exists. The Git LFS endpoints now require authentication when sign-in is required to view the instance.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-118535

Gitea scoped workflow trust kept after repository transfer

A repository registered by its owner as a source of scoped workflows kept that registration when it was transferred to another owner. The new owner could then change the workflows in the transferred repository, and they kept running in the previous owner's repositories with access to their Actions secrets and job tokens. A transfer now removes the owner-level registrations of the repository, and registrations whose source repository no longer belongs to the registering owner are ignored.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-118389

Gitea RubyGems compact index injection through package metadata

The RubyGems package registry accepted gems whose platform, dependency names or dependency version requirements contain newline characters. Because the compact index served to clients is line-based, a user who can publish a gem to an owner's registry could forge index entries, such as packages that do not exist or additional versions of an existing gem with dependencies of their choice. Clients that resolve gems from that registry could then be led to install attacker-chosen dependencies. Gems with such metadata are now rejected.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-125423

Gitea command execution through repository auto-initialization

A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repository already contained. A user who is allowed to create repositories could push a crafted tree during that window so that writing the README followed a symbolic link and overwrote a server-side git hook, which runs commands as the Gitea system user. The initial commit is now built in a freshly initialized directory, and a new repository only becomes ready, and accepts pushes, once its initialization is complete.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—

CVE-2026-123006

Gitea password hash disclosure through repository search

The repository search used by the dashboard (`GET /repo/search`) returned the internal commit status object of each repository. Since 28.0.0 that object included the repository owner's full user record, so any signed-in user could read the password hash, salt and email address of the owner of any repository they can see that has a commit status. The response now contains only the state and target URL of the commit status.

CVSS n/a EPSS n/a KEV · Not listed

Vendors

—

Products

—