Gitea vulnerabilities
210 CVEs and advisories name Gitea as an affected vendor, 1 of them on CISA's Known Exploited Vulnerabilities catalog, newest first. Follow it as a feed.
- CVE-2026-22874Gitea webhook and migration allow-list filtering permits SSRF
- CVE-2026-22555Gitea organization forks can expose organization secrets without create permission
- CVE-2026-22547Gitea repository creation accepts invalid field values
- CVE-2026-20909Gitea tracked-time list endpoint has insufficient permission checks
- CVE-2026-20896Gitea Docker image trusts spoofable reverse-proxy headers by default
- CVE-2026-20779Gitea TOTP single-use enforcement defect allows OTP replay
- CVE-2026-20706Gitea repository archive downloads bypass token scope checks
- CVE-2026-58053Gitea act_runner - Container Hardening Bypass via Workflow Container Options
- CVE-2026-20912Gitea: Cross-Repository Authorization Bypass via Release Attachment Linking Leads to Private Attachment Disclosure
- CVE-2026-20904Gitea: Broken access control in OpenID visibility toggle enables cross-user visibility changes
- CVE-2026-20897Gitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)
- CVE-2026-20888Gitea Pull Requests Auto-Merge: Read-Only Users Can Cancel Scheduled Auto-Merge via Web Endpoint (Authorization Bypass)
- CVE-2026-20883Gitea Stopwatch API Missing Authorization Check Leads to Post-Revocation Information Disclosure
- CVE-2026-20800Notification API Leaks Private Repository Issue Titles After Collaborator Permission Revocation
- CVE-2026-20750Gitea Organization Projects Cross-Organization Authorization Bypass via Project ID (IDOR)
- CVE-2026-20736Gitea Web Attachment Deletion: Cross-Repository Unauthorized Deletion via Missing Repo Ownership Check
- CVE-2026-0798Gitea Release Email Notifications Leak Private Repository Release Details After Access Revocation
- CVE-2025-69413In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists.
- CVE-2025-68946In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS.
- CVE-2025-68945In Gitea before 1.21.2, an anonymous user can visit a private user's project.
- CVE-2025-68944Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries.
- CVE-2025-68943Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order.
- CVE-2025-68942Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text.
- CVE-2025-68941Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources.
- CVE-2025-68940In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request.
- CVE-2025-68939Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API.
- CVE-2025-68938Gitea before 1.25.2 mishandles authorization for deletion of releases.
- CVE-2024-6886Inproper Sanitation of field leading to stored XSS
- CVE-2019-1010261Gitea 1.7.0 and earlier is affected by: Cross Site Scripting (XSS).
- CVE-2019-1010314Gitea 1.7.2, 1.7.3 is affected by: Cross Site Scripting (XSS).