DeutschShown in its original language — a full translation is planned for a future version.
Gitea: Mehrere Schwachstellen
view advisory published 2026-03-16
Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen oder andere, nicht näher spezifizierte Angriffe durchzuführen.
01
describes (15)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-28705US | — | — | ||
Gitea versions before 1.25.5 use release tag names and asset names as filesystem path components when dumping release assets, allowing specially crafted names to affect dump output… | ||||
| CVE-2026-27779US | — | — | ||
Gitea versions before 1.25.5 accept malformed or injected forwarded-proto values when detecting public URLs, allowing spoofed canonical URL generation. | ||||
| CVE-2026-27660US | — | — | ||
Gitea versions before 1.25.5 allow draft release data or attachments to be accessed without the required write permission. | ||||
| CVE-2026-27657US | — | — | ||
Gitea versions before 1.25.5 allow a user to change another user's primary email address. | ||||
| CVE-2026-26307US | — | — | ||
Gitea versions before 1.25.5 do not enforce a timeout on git grep searches, allowing expensive searches to consume server resources. | ||||
| CVE-2026-26292US | — | — | ||
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… | ||||
| CVE-2026-26247US | — | — | ||
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-26232US | —OT elevated | — | ||
Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange. | ||||
| CVE-2026-25782US | — | — | ||
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 a… | ||||
| CVE-2026-25779US | — | — | ||
Gitea versions up to and including 1.25.4 allow redirect bypasses through raw or percent-encoded backslashes in redirect_to values. | ||||
| CVE-2026-25718US | — | — | ||
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-regul… | ||||
| CVE-2026-25712US | — | — | ||
Gitea versions before 1.25.5 have insufficient visibility checks in organization permission APIs for hidden members and private organizations. | ||||
| CVE-2026-24690US | — | — | ||
Gitea versions before 1.25.5 have insufficient permission checks for updating or rebasing pull request branches. | ||||
| CVE-2026-22547US | — | — | ||
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-20909US | — | — | ||
Gitea versions before 1.25.5 have insufficient permission checks when listing tracked time entries. | ||||
02
references
External citations — patches, advisories, analysis.
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan