Skip to content
OpenAdvisories
High WID-SEC-2026-4586 20 CVEs

Gitea: Mehrere Schwachstellen

Published Nov 15, 2026 · Updated Nov 15, 2026 · de

Summary

Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um beliebigen Code mit den Berechtigungen des Betriebssystemkontos auszuführen, auf dem Gitea läuft, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren und offenzulegen, einen Denial-of-Service-Zustand auszulösen oder Cross-Site-Scripting-Angriffe durchzuführen.

Product

Gitea ist ein quelloffener Github-Klon.

Vulnerabilities 20

  • Unscored —

    The RubyGems package registry accepted gems whose platform, dependency names or dependency version requirements contain…

  • Unscored —

    A repository registered by its owner as a source of scoped workflows kept that registration when it was transferred to …

  • Unscored —

    With `REQUIRE_SIGNIN_VIEW = true`, the Git LFS endpoints still answered unauthenticated requests for repositories that …

  • Unscored —

    The popup shown when hovering an issue reference loaded its data from the path of the hovered link and inserted part of…

  • Unscored —

    When a container blob upload was rejected, for example because it exceeded a package size quota, the cleanup removed th…

  • Unscored —

    Gitea accepted an unlimited number of wrong TOTP passcodes during sign-in, in the password reset flow and for Basic aut…

  • Unscored —

    The repository search used by the dashboard (`GET /repo/search`) returned the internal commit status object of each rep…

  • Unscored —

    When a file is edited in a fork through the web editor, Gitea can first copy a branch from the base repository into the…

  • Unscored —

    When a release was edited, the files of the attachments to remove were deleted by the identifiers submitted in the form…

  • Unscored —

    The "Protected file patterns" setting of a branch protection rule was checked against file names as git prints them, an…

  • Unscored —

    The AGit flow (pushing to `refs/for/...`) did not check the pusher's access to pull requests again when it created the …

  • Unscored —

    A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was …

  • Unscored —

    `GET /api/v1/users/{username}/orgs/{org}/permissions` only checked that the organization is visible to the caller and t…

  • Unscored —

    Replying to a code review comment accepted a review ID that belongs to a different pull request, through the web form, …

  • Unscored —

    A pull request review created through the API as a draft (`event` set to `PENDING` or left empty) was added to the pull…

  • Unscored —

    When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After …

  • Unscored —

    Removing a team's review request looked up a review by the negated team ID, which for the team with ID 2 is the ID of t…

  • Unscored —

    Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the …

  • Unscored —

    The web endpoint that removes an attachment skipped the permission check when the request came from the user who had up…

  • Unscored —

    Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. A us…

Revision history

  1. #1

    Initiale Fassung

References