VYPR

Bitnami package

gitea

pkg:bitnami/gitea

Vulnerabilities (73)

  • CVE-2025-69413MedJan 1, 2026
    affected < 1.25.2fixed 1.25.2

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

  • CVE-2025-68946MedDec 26, 2025
    affected < 1.20.1fixed 1.20.1

    In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS.

  • CVE-2025-68945MedDec 26, 2025
    affected < 1.21.2fixed 1.21.2

    In Gitea before 1.21.2, an anonymous user can visit a private user's project.

  • CVE-2025-68944MedDec 26, 2025
    affected < 1.22.2fixed 1.22.2

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

  • CVE-2025-68943MedDec 26, 2025
    affected < 1.21.8fixed 1.21.8

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

  • CVE-2025-68942MedDec 26, 2025
    affected < 1.22.2fixed 1.22.2

    Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text.

  • CVE-2025-68941MedDec 26, 2025
    affected < 1.22.3fixed 1.22.3

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

  • CVE-2025-68940LowDec 26, 2025
    affected < 1.22.5fixed 1.22.5

    In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request.

  • CVE-2025-68939HigDec 26, 2025
    affected < 1.23.0fixed 1.23.0

    Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API.

  • CVE-2025-68938MedDec 26, 2025
    affected < 1.25.2fixed 1.25.2

    Gitea before 1.25.2 mishandles authorization for deletion of releases.

  • CVE-2022-38795MedAug 7, 2023
    affected < 1.17.2fixed 1.17.2

    In Gitea through 1.17.1, repo cloning can occur in the migration function.

  • CVE-2023-3515MedJul 5, 2023
    affected < 1.19.4fixed 1.19.4

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

  • CVE-2022-46685MedDec 12, 2022
    affected < 1.4.5fixed 1.4.5

    In Jenkins Gitea Plugin 1.4.4 and earlier, the implementation of Gitea personal access tokens did not support credentials masking, potentially exposing them through the build log.

  • CVE-2022-42968CriOct 16, 2022
    affected < 1.17.3fixed 1.17.3

    Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.

  • CVE-2022-38183MedAug 12, 2022
    affected < 1.16.9fixed 1.16.9

    In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to

  • CVE-2022-1928MedMay 29, 2022
    affected < 1.16.9fixed 1.16.9

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

  • CVE-2022-30781HigMay 16, 2022
    affected < 1.16.7fixed 1.16.7

    Gitea before 1.16.7 does not escape git fetch remote.

  • CVE-2022-27313HigMay 3, 2022
    affected >= 1.16.3, < 1.16.4fixed 1.16.4

    An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file.

  • CVE-2022-1058MedMar 24, 2022
    affected < 1.16.5fixed 1.16.5

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

  • CVE-2021-29134MedMar 15, 2022
    affected < 1.13.6fixed 1.13.6

    The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL.