| CVE-2026-58424 |
Permanent Fork PR Workflow Approval Gate Bypass
|
8.9
High
|
Jul 3, 2026 |
| CVE-2026-58418 |
SSRF via HTTP Redirect in Repository Migration
|
6.5
Medium
|
Jul 3, 2026 |
| CVE-2026-58419 |
Notification API leaks private issue metadata after access revocation
|
7.5
High
|
Jul 3, 2026 |
| CVE-2026-58421 |
Unauthenticated ReDoS via CODEOWNERS pattern matching allows denial of service
|
7.5
High
|
Jul 3, 2026 |
| CVE-2026-28744 |
Gitea versions up to and including 1.26.1 allow Git smart HTTP requests authenticated with bearer tokens to bypass…
|
8.1
High
|
Jul 3, 2026 |
| CVE-2026-28737 |
Gitea versions from 1.25.0 before 1.26.0 allow stored cross-site scripting through the extensionsRequired field in…
|
8.7
High
|
Jul 3, 2026 |
| CVE-2026-28740 |
Gitea versions up to and including 1.26.2 allow Git LFS object reuse to authorize private source objects for users who…
|
7.1
High
|
Jul 3, 2026 |
| CVE-2026-28705 |
Gitea versions before 1.25.5 use release tag names and asset names as filesystem path components when dumping release…
|
5.3
Medium
|
Jul 3, 2026 |
| CVE-2026-27783 |
Gitea versions up to and including 1.26.1 do not enforce repository-unit authorization on issue-template API endpoints
|
4.3
Medium
|
Jul 3, 2026 |
| CVE-2026-28699 |
Gitea versions up to and including 1.26.1 allow OAuth2 access token scope enforcement to be bypassed through HTTP…
|
8.1
High
|
Jul 3, 2026 |
| CVE-2026-27775 |
Gitea 1.25.5 caches a branch-specific write-permission result across multiple refs in one pre-receive hook session,…
|
8.8
High
|
Jul 3, 2026 |
| CVE-2026-27779 |
Gitea versions before 1.25.5 accept malformed or injected forwarded-proto values when detecting public URLs, allowing…
|
7.5
High
|
Jul 3, 2026 |
| CVE-2026-27780 |
Gitea versions before 1.26.0 do not fail closed on bufio.Scanner errors while processing pre-receive hook input,…
|
9.8
Critical
|
Jul 3, 2026 |
| CVE-2026-27660 |
Gitea versions before 1.25.5 allow draft release data or attachments to be accessed without the required write…
|
7.5
High
|
Jul 3, 2026 |
| CVE-2026-27761 |
Gitea versions up to and including 1.26.2 allow repository RSS and Atom feed endpoints to bypass API access token…
|
4.3
Medium
|
Jul 3, 2026 |
| CVE-2026-27771 |
Gitea versions up to and including 1.26.1 have insufficient permission checks for Composer package source links, which…
|
8.2
High
|
Jul 3, 2026 |
| CVE-2026-27657 |
Gitea versions before 1.25.5 allow a user to change another user's primary email address
|
7.5
High
|
Jul 3, 2026 |
| CVE-2026-26292 |
Gitea versions before 1.25.5 do not use the migration HTTP transport for LFS push and sync mirror operations,…
|
9.8
Critical
|
Jul 3, 2026 |
| CVE-2026-26307 |
Gitea versions before 1.25.5 do not enforce a timeout on git grep searches, allowing expensive searches to consume…
|
7.5
High
|
Jul 3, 2026 |
| CVE-2026-26231 |
Gitea versions up to and including 1.26.1 allow the Allow edits from maintainers permission path to authorize commits to…
|
8.5
High
|
Jul 3, 2026 |
| CVE-2026-26232 |
Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during…
|
9.1
Critical
|
Jul 3, 2026 |
| CVE-2026-26247 |
Gitea versions before 1.25.5 do not persist the OAuth2 PKCE S256 challenge method correctly during authorization,…
|
9.1
Critical
|
Jul 3, 2026 |
| CVE-2026-25718 |
Gitea versions before 1.25.5 mishandle path resolution during template repository generation, allowing template…
|
9.1
Critical
|
Jul 3, 2026 |
| CVE-2026-25779 |
Gitea versions up to and including 1.25.4 allow redirect bypasses through raw or percent-encoded backslashes in…
|
6.1
Medium
|
Jul 3, 2026 |
| CVE-2026-25782 |
Gitea versions before 1.25.5 look up tracked-time entries by time ID without scoping the lookup to the issue in the…
|
5.3
Medium
|
Jul 3, 2026 |