VYPR

Gitea

by Go Gitea

Source repositories

CVEs (146)

  • CVE-2026-26307HigJul 3, 2026
    risk 0.00cvss 7.5epss 0.00

    Gitea versions before 1.25.5 do not enforce a timeout on git grep searches, allowing expensive searches to consume server resources.

  • CVE-2026-26292CriJul 3, 2026
    risk 0.00cvss 9.8epss 0.00

    Gitea versions before 1.25.5 do not use the migration HTTP transport for LFS push and sync mirror operations, bypassing the configured migration transport protections for those LFS requests.

  • CVE-2026-26247CriJul 3, 2026
    risk 0.00cvss 9.1epss 0.00

    Gitea versions before 1.25.5 do not persist the OAuth2 PKCE S256 challenge method correctly during authorization, allowing token exchange without the expected verifier check.

  • CVE-2026-26232CriJul 3, 2026
    risk 0.00cvss 9.1epss 0.00

    Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange.

  • CVE-2026-25782MedJul 3, 2026
    risk 0.00cvss 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-25718CriJul 3, 2026
    risk 0.00cvss 9.1epss 0.00

    Gitea versions before 1.25.5 mishandle path resolution during template repository generation, allowing template processing to read or write through symlinked or otherwise non-regular paths.

  • CVE-2026-25712HigJul 3, 2026
    risk 0.00cvss 7.5epss 0.00

    Gitea versions before 1.25.5 have insufficient visibility checks in organization permission APIs for hidden members and private organizations.

  • CVE-2026-24690HigJul 3, 2026
    risk 0.00cvss 7.5epss 0.00

    Gitea versions before 1.25.5 have insufficient permission checks for updating or rebasing pull request branches.

  • CVE-2026-24451HigJul 3, 2026
    risk 0.00cvss 7.5epss 0.00

    Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.

  • CVE-2026-22874CriJul 3, 2026
    risk 0.00cvss 9.6epss 0.01

    Gitea versions up to and including 1.26.2 have incomplete SSRF protection in webhook and migration allow-list filtering.

  • CVE-2026-22547CriJul 3, 2026
    risk 0.00cvss 9.1epss 0.00

    Gitea versions before 1.25.5 lack validation constraints for repository creation fields, including length-limited template fields and trust model or object format values.

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

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

  • CVE-2026-58053CriJun 28, 2026
    risk 0.00cvss 9.9epss 0.00

    Gitea act_runner with the Docker backend (through act 0.262.0) passes a workflow's container.options string to the Docker job container's HostConfig and, when configured with privileged: false, forces only the Privileged flag off while merging options such as --pid=host,…

  • CVE-2021-29134MedMar 15, 2022
    risk 0.00cvss 5.3epss 0.01

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

  • CVE-2021-45331CriFeb 9, 2022
    risk 0.00cvss 9.8epss 0.01

    An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which could let a malicious user gain privileges. If captured, the TOTP code for the 2FA can be submitted correctly more than once.

  • CVE-2021-45330CriFeb 9, 2022
    risk 0.00cvss 9.8epss 0.01

    An issue exsits in Gitea through 1.15.7, which could let a malicious user gain privileges due to client side cookies not being deleted and the session remains valid on the server side for reuse.

  • CVE-2021-45329MedFeb 8, 2022
    risk 0.00cvss 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-2021-45326HigFeb 8, 2022
    risk 0.00cvss 8.8epss 0.01

    Cross Site Request Forgery (CSRF) vulnerability exists in Gitea before 1.5.2 via API routes.This can be dangerous especially with state altering POST requests.

  • CVE-2021-45325HigFeb 8, 2022
    risk 0.00cvss 7.5epss 0.01

    Server Side Request Forgery (SSRF) vulneraility exists in Gitea before 1.7.0 using the OpenID URL.

  • CVE-2021-3382HigFeb 5, 2021
    risk 0.00cvss 7.5epss 0.02

    Stack buffer overflow vulnerability in gitea 1.9.0 through 1.13.1 allows remote attackers to cause a denial of service (crash) via vectors related to a file path.

Page 7 of 8