VYPR

Gitea

by Go Gitea

Source repositories

CVEs (265)

  • CVE-2026-25779MedJul 3, 2026
    risk 0.40cvss 6.1epss 0.00

    Gitea versions up to and including 1.25.4 allow redirect bypasses through raw or percent-encoded backslashes in redirect_to values.

  • CVE-2021-45329MedFeb 8, 2022
    risk 0.40cvss 6.1epss 0.01

    Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field.

  • CVE-2019-1010261MedJul 18, 2019
    risk 0.40cvss 6.1epss 0.01

    Gitea 1.7.0 and earlier is affected by: Cross Site Scripting (XSS). The impact is: Attacker is able to have victim execute arbitrary JS in browser. The component is: go-get URL generation - PR to fix: https://github.com/go-gitea/gitea/pull/5905. The attack vector is: victim must…

  • CVE-2026-86684HigOct 6, 2026
    risk 0.39cvss 7.1epss 0.00

    The Gitea push mirror API checked whether the repository owner, instead of the requesting user, may use local file system paths. On instances with `[security] IMPORT_LOCAL_PATHS = true`, a repository administrator who is not allowed to import local paths could add a push mirror…

  • CVE-2026-79960HigOct 6, 2026
    risk 0.39cvss 7.1epss 0.00

    When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated the owner instead of the deploy key. A holder of a writable deploy key could create protected tags without being on the…

  • CVE-2026-58437HigAug 13, 2026
    risk 0.39cvss 7.1epss 0.00

    Repository Visibility Manipulation via Git Push Options

  • CVE-2026-58416HigAug 13, 2026
    risk 0.39cvss 7.1epss 0.00

    Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard)

  • CVE-2026-28740HigJul 3, 2026
    risk 0.39cvss 7.1epss 0.00

    Gitea versions up to and including 1.26.2 allow Git LFS object reuse to authorize private source objects for users who have repository access but lack Code-unit access.

  • CVE-2026-20779HigJul 3, 2026
    risk 0.39cvss 7.1epss 0.00

    Gitea versions from 1.5.0 before 1.26.3 have a TOTP single-use enforcement defect that allows a valid TOTP code to be accepted more than once across web two-factor authentication flows and the Basic Auth X-Gitea-OTP path.

  • CVE-2022-0905HigMar 10, 2022
    risk 0.39cvss 7.1epss 0.01

    Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.

  • CVE-2026-123065MedNov 15, 2026
    risk 0.37cvss 5.7epss 0.00

    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…

  • CVE-2026-58440MedAug 13, 2026
    risk 0.37cvss 6.8epss 0.00

    Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo content (incomplete revocation cleanup in `DeleteCollaboration`)

  • CVE-2022-1058MedMar 24, 2022
    risk 0.37cvss 6.1epss 0.53

    Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5.

  • CVE-2026-118535MedNov 15, 2026
    risk 0.36cvss 5.5epss 0.00

    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…

  • CVE-2026-129525MedNov 15, 2026
    risk 0.35cvss 5.4epss 0.00

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

  • CVE-2026-129341MedNov 15, 2026
    risk 0.35cvss 5.4epss 0.00

    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…

  • CVE-2026-128359MedNov 15, 2026
    risk 0.35cvss 5.4epss 0.00

    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…

  • CVE-2026-120729MedNov 15, 2026
    risk 0.35cvss 5.4epss 0.00

    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…

  • CVE-2026-118504MedNov 1, 2026
    risk 0.35cvss 6.5epss 0.00

    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, close or delete…

  • CVE-2026-118386MedNov 1, 2026
    risk 0.35cvss 6.5epss 0.00

    Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository…

Page 7 of 14