CVE-2026-109844 Gitea watched repositories API disclosure after access revocation

GET /api/v1/user/subscriptions returned the metadata of every repository a user was watching without checking that the user still had access to it. A user who watched a private repository while having access, and later lost it, for example through a team permission downgrade, could still read its...

CVE-2026-107686 Gitea reactions accepted on locked issues and comments

The Gitea web handlers for adding and removing reactions on issues and comments did not refuse locked issues for users without write access, although the API did. A signed-in user who could read an issue could therefore add or remove reactions on a locked issue and its comments, bypassing the...

CVE-2026-107686

The Gitea web handlers for adding and removing reactions on issues and comments fail to enforce restrictions on locked issues for users without write access. While the API correctly refuses these actions, the web interface allows a signed-in user with read access to bypass the lock and modify rea...

CVE-2026-107686 Gitea reactions accepted on locked issues and comments

The Gitea web handlers for adding and removing reactions on issues and comments did not refuse locked issues for users without write access, although the API did. A signed-in user who could read an issue could therefore add or remove reactions on a locked issue and its comments, bypassing the...

CVE-2026-107618

The Gitea application is vulnerable to a cross-site request forgery (CSRF) vulnerability affecting repository topics. The issue occurs because the POST /{owner}/{repo}/topics endpoint was registered without the necessary sign-in middleware that provides cross-origin protection. Consequently, a re...

CVE-2026-107618 Gitea cross-site request forgery on repository topics

POST /owner/repo/topics was registered without the sign-in middleware that provides the cross-origin protection, so a request issued by a third-party site was not rejected. A repository administrator who visited a malicious page could have the topics of their repository changed. No other reposito...

CVE-2026-107618 Gitea cross-site request forgery on repository topics

POST /owner/repo/topics was registered without the sign-in middleware that provides the cross-origin protection, so a request issued by a third-party site was not rejected. A repository administrator who visited a malicious page could have the topics of their repository changed. No other reposito...

CVE-2026-105964 Gitea Actions artifact v4 API unbounded request body

The Gitea Actions artifact v4 Twirp handlers read the whole request body into memory without a size limit. A user who can run a workflow and obtains the runner token of that run could send an oversized request to the artifact service and exhaust the memory of the server, which terminates the Gite...

CVE-2026-105964 Gitea Actions artifact v4 API unbounded request body

The Gitea Actions artifact v4 Twirp handlers read the whole request body into memory without a size limit. A user who can run a workflow and obtains the runner token of that run could send an oversized request to the artifact service and exhaust the memory of the server, which terminates the Gite...

CVE-2026-105964

The Gitea Actions artifact v4 (Twirp) handlers are vulnerable to memory exhaustion because they read the entire request body into memory without an enforced size limit. An attacker who can execute a workflow and obtain a runner token can send an oversized request to the artifact service, exhausti...

CVE-2026-105661 Gitea panic on the repositories route of individual users

Requesting /username/-/repositories for an individual user instead of an organization made the organization home handler dereference a nil organization and panic. The request needs no authentication and no special configuration. The server answered with an HTTP 500 error and logged a panic for ea...

CVE-2026-105661

The Gitea platform is vulnerable to a NULL pointer dereference (CWE-476) and an uncaught exception (CWE-248). When an unauthenticated user requests /{username}/-/repositories for an individual user instead of an organization, the organization home handler dereferences a nil organization object. T...

CVE-2026-105661 Gitea panic on the repositories route of individual users

Requesting /username/-/repositories for an individual user instead of an organization made the organization home handler dereference a nil organization and panic. The request needs no authentication and no special configuration. The server answered with an HTTP 500 error and logged a panic for ea...

CVE-2026-109553 Gitea SSH certificate principal impersonation of other users

Gitea resolved the principals of an SSH certificate by searching the content of all stored public keys instead of only principal keys. When Gitea trusts a user certificate authority SSHTRUSTEDUSERCAKEYS and accepts arbitrary principals SSHAUTHORIZEDPRINCIPALSALLOW=anything, a user could register...

CVE-2026-109553

The Gitea SSH server is vulnerable to principal impersonation due to an incorrect logic in how it resolves SSH certificate principals. The software incorrectly searches the content of all stored public keys instead of only the principal keys. This issue occurs when Gitea trusts a user certificate...

CVE-2026-109553 Gitea SSH certificate principal impersonation of other users

Gitea resolved the principals of an SSH certificate by searching the content of all stored public keys instead of only principal keys. When Gitea trusts a user certificate authority SSHTRUSTEDUSERCAKEYS and accepts arbitrary principals SSHAUTHORIZEDPRINCIPALSALLOW=anything, a user could register...

CVE-2026-104627

The Gitea OpenID association callback in the security settings is vulnerable to account hijacking because it accepts positive OpenID 2.0 assertions without verifying that the signed-in user initiated the linking process. Due to the nature of unsolicited assertions, an attacker controlling an Open...

CVE-2026-104627 Gitea OpenID account linking without session binding

The Gitea OpenID association callback in the security settings accepted a positive OpenID 2.0 assertion without checking that the signed-in user had started the linking. Because OpenID 2.0 allows unsolicited assertions, an attacker-controlled OpenID provider could attach the attacker's identity t...

CVE-2026-104627 Gitea OpenID account linking without session binding

The Gitea OpenID association callback in the security settings accepted a positive OpenID 2.0 assertion without checking that the signed-in user had started the linking. Because OpenID 2.0 allows unsolicited assertions, an attacker-controlled OpenID provider could attach the attacker's identity t...

PT-2026-117157

Name of the Vulnerable Software and Affected Versions Gitea versions prior to 1.27.3 Gitea versions prior to 28.0.0 Description Seven API endpoints under /api/v1/users/username followers, following, following/target, starred, subscriptions, keys, and gpg keys were registered without the...