VYPR

Bitnami package

gitea

pkg:bitnami/gitea

Vulnerabilities (73)

  • CVE-2026-104636HigOct 6, 2026
    affected < 28.0.0fixed 28.0.0

    Gitea validated the initial remote URL for push mirrors, wiki remote checks, and fetches of migrated pull request heads, but the subsequent raw Git operations followed HTTP redirects without revalidating the destination. A repository administrator using a policy-allowed endpoint

  • CVE-2026-104632HigOct 6, 2026
    affected < 28.0.0fixed 28.0.0

    Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with Acti

  • CVE-2026-104626HigOct 6, 2026
    affected < 28.0.0fixed 28.0.0

    A user who can open a fork pull request can place workflow content with a shared run-level concurrency group into a Gitea Actions run that is awaiting approval. When a later run in that group cancels the blocked job, the run becomes terminal while still marked as needing approval

  • CVE-2026-103670HigOct 6, 2026
    affected < 28.0.0fixed 28.0.0

    When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from

  • CVE-2026-103667MedOct 6, 2026
    affected < 28.0.0fixed 28.0.0

    Gitea's container registry served blob downloads with a `Content-Type` taken from the media type declared in pushed image manifests, without a `Content-Disposition` or restrictive content security policy. A user who can push container images can publish a blob containing HTML and

  • CVE-2026-103059CriOct 6, 2026
    affected < 28.0.0fixed 28.0.0

    When Gitea's built-in SSH server is enabled (`START_SSH_SERVER = true`), the presented public key was looked up with an SQL `LIKE` comparison of its encoded content, which is case-insensitive on some databases, including the default SQLite. An attacker who can construct a case va

  • CVE-2026-101029MedOct 6, 2026
    affected < 28.0.0fixed 28.0.0

    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 mirror

  • CVE-2026-101027HigOct 6, 2026
    affected < 28.0.0fixed 28.0.0

    When `[migrations] ALLOWED_DOMAINS` was configured, a hostname matching the allow list was accepted without checking its resolved address against the local-network restrictions. A user who can start repository migrations and control the DNS of an allowed hostname could make it re

  • CVE-2026-60004CriKEVAug 26, 2026
    affected >= 1.17.0, < 1.27.1fixed 1.27.1

    Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.

  • CVE-2026-59765HigAug 13, 2026
    affected < 1.27.0fixed 1.27.0

    SSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud Metadata

  • CVE-2026-34966HigAug 5, 2026
    affected < 1.27.0fixed 1.27.0

    Gitea prior to 1.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to bypass SSRF protections by exploiting HTTP fetch operations in migration and OAuth avatar code paths that use Go's default http.Get without a custom DialContext. Atta

  • CVE-2026-20912CriJan 22, 2026
    affected < 1.25.4fixed 1.25.4

    Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users.

  • CVE-2026-20904MedJan 22, 2026
    affected < 1.25.4fixed 1.25.4

    Gitea does not properly validate ownership when toggling OpenID URI visibility. An authenticated user may be able to change the visibility settings of other users' OpenID identities.

  • CVE-2026-20897CriJan 22, 2026
    affected < 1.25.4fixed 1.25.4

    Gitea does not properly validate repository ownership when deleting Git LFS locks. A user with write access to one repository may be able to delete LFS locks belonging to other repositories.

  • CVE-2026-20888MedJan 22, 2026
    affected < 1.25.4fixed 1.25.4

    Gitea does not properly verify authorization when canceling scheduled auto-merges via the web interface. A user with read access to pull requests may be able to cancel auto-merges scheduled by other users.

  • CVE-2026-20883MedJan 22, 2026
    affected < 1.25.4fixed 1.25.4

    Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches.

  • CVE-2026-20800MedJan 22, 2026
    affected < 1.25.4fixed 1.25.4

    Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications.

  • CVE-2026-20750CriJan 22, 2026
    affected < 1.25.4fixed 1.25.4

    Gitea does not properly validate project ownership in organization project operations. A user with project write access in one organization may be able to modify projects belonging to a different organization.

  • CVE-2026-20736HigJan 22, 2026
    affected < 1.25.4fixed 1.25.4

    Gitea does not properly verify repository context when deleting attachments. A user who previously uploaded an attachment to a repository may be able to delete it after losing access to that repository by making the request through a different repository they can access.

  • CVE-2026-0798LowJan 22, 2026
    affected < 1.25.4fixed 1.25.4

    Gitea may send release notification emails for private repositories to users whose access has been revoked. When a repository is changed from public to private, users who previously watched the repository may continue to receive release notifications, potentially disclosing relea