Skip to content
OpenAdvisories
High WID-SEC-2026-3079 25 CVEs

Gitea: Mehrere Schwachstellen ermöglichen Ausführen von beliebigem Programmcode

Published Aug 30, 2026 · Updated Oct 14, 2026 · Revision 2 · de-DE

Summary

Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder Denial-of-Service-Zustände zu verursachen.

Product

Gitea ist ein quelloffener Github-Klon.

Vulnerabilities 25

  • High 8.8

    Gitea fork workflow approval bypass through review events

    Gitea's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the run as originating from a fork. Review comment and review approval or rejection events can consequentl…

  • High 8.1

    Gitea fork workflow approval bypass through concurrency cancellation

    Gitea enforces first-time fork contributor approval by blocking jobs, but some job transition and dispatch paths do not re-check the run's approval requirement. A separate run sharing a job-level concurrency group can cancel a pending job and cause its blocke…

  • Medium 6.5

    Gitea organization team policy bypass through repository API

    Gitea's repository-side team-link API allows a repository administrator who is not an organization owner to attach organization teams to a repository despite RepoAdminChangeTeamAccess being disabled. The endpoint does not enforce the organization's restrictio…

  • Medium 6.5

    Gitea OneDev migration denial of service

    Gitea's OneDev migration downloader reads the entire remote version response into memory without a size limit and uses a client without a timeout. An authenticated user who can start a repository migration can direct it to an attacker-controlled OneDev-compat…

  • Medium 6.5

    Gitea GitLab migration denial of service

    Gitea's initial GitLab migration version probe uses an HTTP client without a timeout and does not attach the migration task's cancellation context. An authenticated user who can start migrations can target an attacker-controlled server that keeps the response…

  • Medium 6.5

    Gitea Alpine package parsing memory exhaustion

    Gitea parses Alpine package uploads before enforcing package-size quotas and does not bound the decompressed .PKGINFO data or its dependency and provides entry counts. An authenticated user with package-publish permission can upload a small, highly compressed…

  • Medium 6.5

    Gitea Swift package manifest memory exhaustion

    Gitea's Swift package parser limits each manifest to 128 KiB but does not limit the number of manifests or their aggregate size before reading them into memory. An authenticated user with package-publish permission can upload a highly compressed archive conta…

  • Medium 6.5

    Gitea required Actions check bypass through skipped workflows

    For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped status when workflow branch or path filters exclude execution. A fork pull request author can supply a workflow matching a required status conte…

  • Medium 6.5

    Gitea private comparison disclosure with public-only tokens

    Gitea's shared comparison helper omits the token repository-access check used when updating pull requests. A public-only token with read:repository scope can route a comparison or pull request creation through a public base repository and retrieve commit hist…

  • Medium 5.9

    Gitea private attachment disclosure through repository mismatch

    Gitea's web attachment handler skips its cross-repository ownership check for attachments created before 16 January 2026 and checks permissions against the repository named in the request URL instead. An unauthenticated attacker who knows a private attachment…

  • Medium 5.8

    Gitea local code execution through writable Git hooks

    Gitea creates server-side Git hook directories and scripts with mode 0777 and relies on the process umask to restrict access. With a permissive umask such as 0000 or 0002, another local user who can reach the repository storage may modify a hook or add an exe…

  • Medium 5.4

    Gitea organization repository creation token scope bypass

    Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can therefore c…

  • Medium 5.4

    Gitea private migration creation with public-only tokens

    Gitea's repository migration API accepts a public-only token when the request specifies creation of a private repository. A delegated token intended to operate only on public resources can create a private repository and migration task under the authorizing a…

  • Medium 5.3

    Gitea private reusable workflow disclosure to fork runs

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

  • Medium 5.3

    Gitea hidden-owner repository listing disclosure

    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 …

  • Medium 4.3

    Gitea restricted-user package visibility bypass

    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 …

  • Medium 4.3

    Gitea restricted-user organization metadata disclosure

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

  • Medium 4.3

    Gitea restricted-user activity and heatmap disclosure

    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 …

  • Medium 4.3

    Gitea restricted-user issue search disclosure

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

  • Medium 4.3

    Gitea restricted-user SSH and GPG key metadata disclosure

    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…

  • Medium 4.3

    Gitea organization listing token scope bypass

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

  • Medium 4.3

    Gitea private pull request title disclosure through markup

    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…

  • Medium 4.3

    Gitea private workflow badge token scope bypass

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

  • Medium 4.3

    Gitea repository initialization resource exhaustion

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

  • Medium 4.3

    Gitea Maven checksum upload quota bypass and memory exhaustion

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

Revision history

  1. #2

    Referenz(en) aufgenommen: EUVD-2026-101083, EUVD-2026-101082, EUVD-2026-101099, EUVD-2026-101094, EUVD-2026-101101, EUVD-2026-101097, EUVD-2026-101095, EUVD-2026-101103, EUVD-2026-101102, EUVD-2026-101088, EUVD-2026-101089, EUVD-2026-101090, EUVD-2026-101091, EUVD-2026-101092, EUVD-2026-101100, EUVD-2026-101098, EUVD-2026-101096, EUVD-2026-101111, EUVD-2026-101081, EUVD-2026-101093, EUVD-2026-101283, EUVD-2026-101284, EUVD-2026-101084, EUVD-2026-101086, EUVD-2026-101087

  2. #1

    Initiale Fassung

References