Vulnerabilidades de Gitea (CVE)

Registros CVE publicados para Gitea, los más recientes primero. Siga el producto para recibir un correo con cada nueva.

227 resultados
5.4Media

Gitea release asset deletion by former writers

Gitea Gitea

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…

5.4Media

Gitea OAuth2 provider tokens issued to disabled users

Gitea Gitea

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…

7.5Alta

Gitea missing attempt limit for TOTP passcodes

Gitea Gitea

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 …

3.7Baja

Gitea anonymous Git LFS access despite required sign-in

Gitea Gitea

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…

5.5Media

Gitea scoped workflow trust kept after repository transfer

Gitea Gitea

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 re…

6.5Media

Gitea password hash disclosure through repository search

Gitea Gitea

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…

4.3Media
CVE-2026-119625

Gitea user and organization feed token scope bypass

Gitea Gitea

The `/{username}` web route accepted personal access tokens over HTTP Basic authentication without checking their scope. A token confined to an unrelated scope, such as `read:issue`, could read its owner's private activity through the user RSS/Atom feed and t…

7.5Alta
CVE-2026-119533

Gitea private pull request disclosure on project boards

Gitea Gitea

Repository and organization project boards listed the pull requests that reference each issue on the board without checking whether the viewer can read them. When a private pull request mentions an issue on a board the viewer can open, the board revealed the …

6.5Media
CVE-2026-118504

Gitea issue changes on archived repositories through the API

Gitea Gitea

The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository is archived. A user allowed to change issues of an archived repository could use the API to edit, c…