code.gitea.io/gitea vulnerabilities (Go)
124 vulnerabilities.
code.gitea.io/giteaGoGitea pre-receive hook permission cache allows full repository write access8.8 Highcode.gitea.io/giteaGoGitea Composer package source links use insufficient permission checks8.2 Highcode.gitea.io/giteaGoGitea repository feeds bypass API token scope enforcement4.3 Mediumcode.gitea.io/giteaGoGitea draft releases use insufficient permission checks7.5 Highcode.gitea.io/giteaGoGitea email settings allow changing another user's primary email address7.5 Highcode.gitea.io/giteaGoGitea git grep search lacks a timeout7.5 Highcode.gitea.io/giteaGoGitea LFS mirror synchronization bypasses migration HTTP transport restrictions9.8 Criticalcode.gitea.io/giteaGoGitea OAuth2 PKCE S256 challenges are not enforced during token exchange9.1 Criticalcode.gitea.io/giteaGoGitea OAuth2 authorization codes lack expiry and reuse enforcement9.1 Criticalcode.gitea.io/giteaGoGitea tracked-time deletion can target entries from another issue5.3 Mediumcode.gitea.io/giteaGoGitea template repository generation mishandles symlinked paths9.1 Criticalcode.gitea.io/giteaGoGitea organization permission APIs expose private visibility information7.5 Highcode.gitea.io/giteaGoGitea private organization labels are visible to unauthorized users7.5 Highcode.gitea.io/giteaGoGitea pull-request branch updates use insufficient permission checks7.5 Highcode.gitea.io/giteaGoGitea fork synchronization can expose private parent repository data7.5 Highcode.gitea.io/giteaGoGitea webhook and migration allow-list filtering permits SSRF9.6 Criticalcode.gitea.io/giteaGoGitea repository creation accepts invalid field values9.1 Criticalcode.gitea.io/giteaGoGitea tracked-time list endpoint has insufficient permission checks5.3 Mediumcode.gitea.io/giteaGoGitea Docker image trusts spoofable reverse-proxy headers by default9.8 Criticalcode.gitea.io/giteaGoGitea TOTP single-use enforcement defect allows OTP replay7.1 Highcode.gitea.io/giteaGoGitea redirect handling permits open redirects through backslash paths6.1 Mediumcode.gitea.io/giteaGoGitea 3D file viewer allows stored XSS through glTF extensionsRequired8.7 Highcode.gitea.io/giteaGoPublic-only tokens bypass private-resource restrictions on `/api/v1/user` self routes8.1 Highcode.gitea.io/giteaGoGitea organization forks can expose organization secrets without create permission8.1 Highcode.gitea.io/giteaGoGitea repository archive downloads bypass token scope checks9.1 Criticalcode.gitea.io/giteaGoGitea issue-template APIs bypass repository unit authorization4.3 Mediumcode.gitea.io/giteaGoGitea user organization API bypasses public-only token filtering4.3 Mediumcode.gitea.io/giteaGoGitea maintainer-edit permissions allow unauthorized commits to readable repositories8.5 Highcode.gitea.io/giteaGoGitea Basic Auth bypasses OAuth2 access token scopes8.1 Highcode.gitea.io/giteaGoGitea Git smart HTTP bypasses repository token scopes for bearer tokens8.1 Highcode.gitea.io/giteaGoGitea has insecure default SSH settings6.3 Mediumcode.gitea.io/giteaGoGitea: Cross-Repository Authorization Bypass via Release Attachment Linking Leads to Private Attachment Disclosure9.1 Criticalcode.gitea.io/giteaGoGitea: Broken access control in OpenID visibility toggle enables cross-user visibility changes6.5 Mediumcode.gitea.io/giteaGoGitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)9.1 Criticalcode.gitea.io/giteaGoGitea Pull Requests Auto-Merge: Read-Only Users Can Cancel Scheduled Auto-Merge via Web Endpoint (Authorization Bypass)4.3 Mediumcode.gitea.io/giteaGoGitea Stopwatch API Missing Authorization Check Leads to Post-Revocation Information Disclosure6.5 Mediumcode.gitea.io/giteaGoNotification API Leaks Private Repository Issue Titles After Collaborator Permission Revocation6.5 Mediumcode.gitea.io/giteaGoGitea Organization Projects Cross-Organization Authorization Bypass via Project ID (IDOR)9.1 Criticalcode.gitea.io/giteaGoGitea Web Attachment Deletion: Cross-Repository Unauthorized Deletion via Missing Repo Ownership Check7.5 Highcode.gitea.io/giteaGoGitea Release Email Notifications Leak Private Repository Release Details After Access Revocation3.5 Lowcode.gitea.io/giteaGoGitea's /api/v1/user endpoint has different responses for failed authentication depending on whether a username exists5.3 Mediumcode.gitea.io/giteaGoGitea vulnerable to Cross-site Scripting5.4 Mediumcode.gitea.io/giteaGoGitea: anonymous user can visit private user's project5.8 Mediumcode.gitea.io/giteaGoGitea sometimes mishandles propagation of token scope for access control within one of its own package registries5.0 Mediumcode.gitea.io/giteaGoGitea inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order5.3 Mediumcode.gitea.io/giteaGoGitea allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text5.4 Mediumcode.gitea.io/giteaGoGitea mishandles access to a private resource upon receiving an API token with scope limited to public resources4.9 Mediumcode.gitea.io/giteaGoGitea doesn't adequately enforce branch deletion permissions after merging a pull request.3.1 Lowcode.gitea.io/giteaGoGitea allows attackers to add attachments with forbidden file extensions8.2 Highcode.gitea.io/giteaGoGitea mishandles authorization for deletion of releases4.3 Medium- Show moreLoading…