VYPR

Vendor CVEs

Go Gitea

All CVEs

265 total · sorted by risk
  • CVE-2022-1928MedMay 29, 2022
    risk 0.28cvss 5.4epss 0.01

    Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9.

  • CVE-2018-1000803MedOct 8, 2018
    risk 0.28cvss 5.3epss 0.01

    Gitea version prior to version 1.5.1 contains a CWE-200 vulnerability that can result in Exposure of users private email addresses. This attack appear to be exploitable via Watch a repository to receive email notifications. Emails received contain the other recipients even if…

  • CVE-2026-114199MedNov 1, 2026
    risk 0.27cvss 5.3epss 0.00

    `GET /api/v1/users/{username}/heatmap` computed the contribution heatmap with the repository access of the token owner and ignored the public-only restriction of the access token, unlike the activity feed endpoints. A holder of a user's public-only token could read contribution…

  • CVE-2026-105661MedOct 18, 2026
    risk 0.27cvss 5.3epss 0.00

    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…

  • CVE-2026-73135MedOct 14, 2026
    risk 0.27cvss 5.3epss 0.00

    Gitea uses inconsistent repository visibility predicates, and the condition used by some repository-listing endpoints admits repositories whose owners are hidden from the viewer. Those listings disclose repository metadata even though direct routes correctly deny access with a…

  • CVE-2026-63792MedOct 14, 2026
    risk 0.27cvss 5.3epss 0.00

    Gitea's collaborative-owner authorization path for reading cross-repository reusable workflows does not exclude fork pull request runs. An approved fork workflow targeting a private repository can read workflow files from another private repository that trusts the base…

  • CVE-2026-58507MedAug 13, 2026
    risk 0.27cvss 5.3epss 0.00

    Private Repository Existence Disclosure via go-get Meta Endpoint

  • CVE-2026-28705MedJul 3, 2026
    risk 0.27cvss 5.3epss 0.00

    Gitea versions before 1.25.5 use release tag names and asset names as filesystem path components when dumping release assets, allowing specially crafted names to affect dump output paths.

  • CVE-2026-25782MedJul 3, 2026
    risk 0.27cvss 5.3epss 0.00

    Gitea versions before 1.25.5 look up tracked-time entries by time ID without scoping the lookup to the issue in the request URL, allowing deletion attempts to target entries from another issue.

  • CVE-2026-20909MedJul 3, 2026
    risk 0.27cvss 5.3epss 0.00

    Gitea versions before 1.25.5 have insufficient permission checks when listing tracked time entries.

  • CVE-2025-69413MedJan 1, 2026
    risk 0.27cvss 5.3epss 0.00

    In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists.

  • CVE-2025-68943MedDec 26, 2025
    risk 0.27cvss 5.3epss 0.00

    Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order.

  • CVE-2025-68944MedDec 26, 2025
    risk 0.26cvss 5.0epss 0.00

    Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries.

  • CVE-2026-97208MedOct 6, 2026
    risk 0.25cvss 4.9epss 0.00

    The Gitea API endpoint for creating push mirrors (`POST /api/v1/repos/{owner}/{repo}/push_mirrors`) checked only whether mirroring was enabled and not the `[mirror] DISABLE_NEW_PUSH` setting that the web interface enforces. A repository administrator could therefore create new…

  • CVE-2026-58429MedAug 13, 2026
    risk 0.25cvss 4.9epss 0.00

    Public-Only Personal access tokens scope bypass in Organization and Permission Endpoints

  • CVE-2025-68941MedDec 26, 2025
    risk 0.25cvss 4.9epss 0.00

    Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources.

  • CVE-2021-28378LowMar 15, 2021
    risk 0.25cvss 3.7epss 0.09

    Gitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations.

  • CVE-2026-120725LowNov 15, 2026
    risk 0.24cvss 3.7epss 0.00

    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…

  • CVE-2026-52807MedJun 24, 2026
    risk 0.24cvss —epss 0.00

    Gogs is an open source self-hosted Git service. Prior to 0.14.3, in new_form.tmpl, milestone names are rendered with Go's default auto-escaping ({{.Name}}), which converts < to < etc. This prevents direct HTML injection. However, when the browser renders the DOM, the text…

  • CVE-2023-3515MedJul 5, 2023
    risk 0.22cvss 4.4epss 0.00

    Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4.

  • CVE-2026-119627MedNov 1, 2026
    risk 0.21cvss 4.3epss 0.00

    The web profile and RSS/Atom feed routes of users and organizations checked only whether a signed-in viewer could see a limited-visibility owner, without considering the `public-only` restriction of the personal access token used to authenticate. Any user holding a public-only…

  • CVE-2026-119625MedNov 1, 2026
    risk 0.21cvss 4.3epss 0.00

    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 the profile activity…

  • CVE-2026-118394MedNov 1, 2026
    risk 0.21cvss 4.3epss 0.00

    The OAuth2 userinfo endpoint (`/login/oauth/userinfo`) decided whether to limit the `groups` claim to public organizations by re-parsing the `Authorization` header as an OAuth2 access token instead of using the scope of the credential that authenticated the request. When a…

  • CVE-2026-117646MedNov 1, 2026
    risk 0.21cvss 4.3epss 0.00

    The repositories, stars and watching tabs of user profiles and the repository list of organization home pages included private repositories for every signed-in request without checking whether the request used a personal access token restricted to public resources…

  • CVE-2026-112887MedNov 1, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea Actions task tokens authenticate to the REST API as a shared system user with a negative ID, which repository, organization, project and key filters treated as having no owner restriction, and the token carried no API scope to restrict user-scoped routes. A user who can…

  • CVE-2026-110311MedOct 18, 2026
    risk 0.21cvss 4.3epss 0.00

    Creating a draft release through the API returned an `assets` list that was built from a release without an ID, which matched every attachment that was not linked to a release. A user who could create a draft release in a repository therefore received the metadata (file name,…

  • CVE-2026-109844MedOct 18, 2026
    risk 0.21cvss 4.3epss 0.00

    `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,…

  • CVE-2026-107686MedOct 18, 2026
    risk 0.21cvss 4.3epss 0.00

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

  • CVE-2026-73273MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's Maven upload handler reads checksum uploads entirely into memory and returns before enforcing package-size quotas. An authenticated user with package-publish permission can submit an oversized body to a checksum endpoint despite legitimate checksum values being at most…

  • CVE-2026-73130MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea does not limit the length of the gitignores field accepted by repository-creation forms and the API. Repository initialization splits the field into template names, repeatedly reads the referenced templates, and buffers their contents in memory. An attacker who can create…

  • CVE-2026-73126MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's Actions workflow status badge endpoint does not enforce repository-read scope or the public-only restriction on the token authenticating the request. A token lacking read:repository, or restricted to public repositories, can retrieve the latest workflow status of a…

  • CVE-2026-71301MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's repository markup endpoint resolves same-repository pull request references without enforcing the viewer's Pull Requests permission. A member with only Wiki access to a private repository can submit a markup preview request and retrieve a private pull request's title and…

  • CVE-2026-70407MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's organization-list API does not enforce the read:organization token scope. A token limited to another category, such as read:misc, can retrieve organization metadata visible to its owner. For a site administrator's token, the response can include Limited and private…

  • CVE-2026-68964MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's user SSH and GPG key-list API endpoints omit the profile visibility check applied by their web equivalents. A restricted account can retrieve public keys, key titles, fingerprints, and GPG-embedded email addresses belonging to Limited-visibility users. The disclosure…

  • CVE-2026-68957MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's API and web issue-search paths do not treat restricted accounts as anonymous viewers when evaluating Limited-visibility repository owners. A restricted user can search and retrieve issue titles and bodies that should be hidden by the owner's visibility policy. Keyword…

  • CVE-2026-67577MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's activity-feed and contribution-heatmap API handlers do not apply the profile visibility check for restricted accounts viewing Limited-visibility users. A restricted user can retrieve activity records and contribution timestamps that the corresponding profile routes deny.…

  • CVE-2026-66853MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's user organization-list API includes Limited-visibility organizations for authenticated restricted accounts without applying the visibility restriction enforced by the single-organization endpoint. A restricted user can list a known user's public organization memberships…

  • CVE-2026-66849MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's package registry grants authenticated users read access to packages owned by Limited-visibility users without excluding restricted accounts. A restricted user can enumerate and download those packages despite the visibility policy that should prevent this access. The…

  • CVE-2026-59766MedOct 14, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's starred-repository and tracked-time API endpoints do not re-check current repository permissions before returning data associated with the requesting user. A user whose access to a private repository has been revoked can still retrieve repository metadata through…

  • CVE-2026-97626MedOct 6, 2026
    risk 0.21cvss 4.3epss 0.00

    Requesting a user or organization profile page (`GET /{username}`) with an `Accept: application/rss+xml` or `Accept: application/atom+xml` header returned the owner's activity feed without the visibility check that the profile page and the `.rss` and `.atom` routes apply.…

  • CVE-2026-105268MedOct 6, 2026
    risk 0.21cvss 4.3epss 0.00

    The Gitea API routes for issue attachments (`/api/v1/repos/{owner}/{repo}/issues/{index}/assets/{attachment_id}`) also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an…

  • CVE-2026-96589MedOct 6, 2026
    risk 0.21cvss 4.3epss 0.00

    When a private repository is transferred to a user who lacks access, Gitea grants that recipient temporary read access as a collaborator so they can review the repository. Rejecting or cancelling the transfer did not revoke this collaboration, so the named recipient kept…

  • CVE-2026-96400MedOct 6, 2026
    risk 0.21cvss 4.3epss 0.00

    With `[migrations] ALLOWED_DOMAINS` set to a matching entry such as `*` or a hostname wildcard, Gitea's migration URL validation could permit reserved and link-local addresses, such as `169.254.169.254`, even when `ALLOW_LOCALNETWORKS = false`. The local-network block list did…

  • CVE-2026-101029MedOct 6, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea's repository migration and pull mirror egress checks could be bypassed with a hostname that returns multiple DNS answers, because the address that was validated was not necessarily the address Git later connected to. A low-privileged user who can create migrations or…

  • CVE-2026-59763MedAug 13, 2026
    risk 0.21cvss 4.3epss 0.00

    Unbounded Arch package file metadata can cause resource amplification in Gitea package uploads

  • CVE-2026-58444MedAug 13, 2026
    risk 0.21cvss 4.3epss 0.00

    Personal access token scope enforcement bypass on the repository home page (`GET /{owner}/{repo}`) discloses private repository contents

  • CVE-2026-58425MedAug 13, 2026
    risk 0.21cvss 4.3epss 0.00

    OAuth token introspection returns metadata of tokens issued to other clients (RFC 7662 section 4 violation)

  • CVE-2026-27783MedJul 3, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea versions up to and including 1.26.1 do not enforce repository-unit authorization on issue-template API endpoints.

  • CVE-2026-27761MedJul 3, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea versions up to and including 1.26.2 allow repository RSS and Atom feed endpoints to bypass API access token scope checks, exposing private repository commit data to tokens without the required repository scope.

  • CVE-2026-25714MedJul 3, 2026
    risk 0.21cvss 4.3epss 0.00

    Gitea versions up to and including 1.26.1 do not apply public-only token filtering consistently to the user organization API, leaving an incomplete fix for CVE-2025-68941.

Page 5 of 6