Repository Visibility Manipulation via Git Push Options
Repository Visibility Manipulation via Git Push Options
Export limit exceeded: 425740 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Repository Visibility Manipulation via Git Push Options
Repository Migration Follows Git HTTP Redirects After URL Allow/Block Validation, Enabling Internal Git Repository Exfiltration
Two SSRF vulnerabilities in Gitea migration/mirror (DNS rebinding + missing re-validation)
ParseAcceptLanguage quadratic-time DoS via Locale middleware on unauthenticated requests
REST API exposes organization membership of private organizations to public
Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API
Private Repository Existence Disclosure via go-get Meta Endpoint
Release attachment extension allowlist bypass via web release edit form (variant of CVE-2025-68939)
Local File Inclusion via file:// URI in Migration Restore
Personal access token scope enforcement bypass on the repository home page (`GET /{owner}/{repo}`) discloses private repository contents
OAuth token introspection returns metadata of tokens issued to other clients (RFC 7662 section 4 violation)
Public-only API token restriction is not enforced on team API routes
OAuth2 sign-in reactivates an administrator-deactivated account on auth sources without refresh tokens (incomplete fix of #38009)
Privilege Escalation via Access Token Scope Escalation in API
Gitea Remember-Me Token Theft Not Invalidating Attacker Session
Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access
Branch Protection Bypass via PR Retargeting Preserves Stale `official` Approval Flag
Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo content (incomplete revocation cleanup in `DeleteCollaboration`)
Cross-repository issue/comment attachment re-linking can expose private attachment content