Gitea Gitea Open Source Git Server

97 vulnérabilités publiées citent ce produit.

Tel que les CNA l’écrivent dans leurs fiches CVE (éditeur et produit) ; les versions sont les leurs.

CVEVersions vulnérablesTitreSévéritéPubliéeEPSSExploitation
CVE-2026-247911.22.3 – 1.26.1Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routesHIGH 8.10.4 %
CVE-2026-24059< 1.25.5Gitea runner registration-token GET endpoint performs a write under a read-only token scopeMEDIUM 6.50.4 %
CVE-2026-59765≤ 1.26.4SSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud MetadataHIGH 7.50.4 %
CVE-2026-59763≤ 1.26.4Unbounded Arch package file metadata can cause resource amplification in Gitea package uploadsMEDIUM 4.30.3 %
CVE-2026-58511≤ 1.26.4Webhook Authorization Header Returned in Plaintext via APILOW 2.70.4 %
CVE-2026-58510≤ 1.26.4GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->privateMEDIUM 4.30.3 %
CVE-2026-58508≤ 1.26.4Two SSRF vulnerabilities in Gitea migration/mirror (DNS rebinding + missing re-validation)CRITICAL 9.10.5 %
CVE-2026-58507≤ 1.26.4Private Repository Existence Disclosure via go-get Meta EndpointMEDIUM 5.30.4 %
CVE-2026-58445≤ 1.26.4Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel APILOW 2.70.4 %
CVE-2026-58444< 1.27.0Personal access token scope enforcement bypass on the repository home page (`GET /{owner}/{repo}`) discloses private repository contentsMEDIUM 4.30.4 %
CVE-2026-58443≤ 1.26.4Public-only repository tokens can update private PR head branchesCRITICAL 9.10.6 %
CVE-2026-58442≤ 1.26.4Repository migration SSRF via multi-answer DNS allow-list bypassMEDIUM 6.50.4 %
CVE-2026-58441≤ 1.26.4SSRF in restore-repo via unsanitized pull_request.yml Head.CloneURLMEDIUM 6.30.2 %
CVE-2026-58440≤ 1.26.4Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo conten…MEDIUM 6.80.5 %
CVE-2026-58439≤ 1.26.4Branch Protection Bypass via PR Retargeting Preserves Stale `official` Approval FlagHIGH 8.10.5 %
CVE-2026-58438≤ 1.26.4Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot accessHIGH 7.50.5 %
CVE-2026-58437≤ 1.26.4Repository Visibility Manipulation via Git Push OptionsHIGH 7.10.3 %
CVE-2026-58436≤ 1.26.4ParseAcceptLanguage quadratic-time DoS via Locale middleware on unauthenticated requestsHIGH 7.50.6 %
CVE-2026-58435≤ 1.26.4Gitea LFS Deploy-Key Privilege EscalationMEDIUM 5.40.3 %
CVE-2026-584341.26.2Private Repository Metadata Remains Accessible After Access RevocationHIGH 7.50.5 %
CVE-2026-58433≤ 1.26.4Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization settingCRITICAL 9.10.5 %
CVE-2026-58432≤ 1.26.4Missing Authorization and Authorization Bypass Through User-Controlled Key and Incorrect Permission Assignment for Critical Resource and …MEDIUM 5.90.4 %
CVE-2026-58431≤ 1.26.4Public-only API token restriction is not enforced on team API routesMEDIUM 4.30.3 %
CVE-2026-58429≤ 1.26.4Public-Only Personal access tokens scope bypass in Organization and Permission EndpointsMEDIUM 4.90.5 %
CVE-2026-58428≤ 1.26.4Release attachment extension allowlist bypass via web release edit form (variant of CVE-2025-68939)MEDIUM 6.50.5 %
CVE-2026-58427≤ 1.26.4Private org member list leaked via /members API endpoint — incomplete fix for PR #38145HIGH 7.50.5 %
CVE-2026-58425≤ 1.26.4OAuth token introspection returns metadata of tokens issued to other clients (RFC 7662 section 4 violation)MEDIUM 4.30.3 %
CVE-2026-58420≤ 1.26.4Local File Inclusion via file:// URI in Migration RestoreMEDIUM 4.40.5 %
CVE-2026-58417≤ 1.26.4REST API exposes organization membership of private organizations to publicHIGH 7.50.5 %
CVE-2026-58416≤ 1.26.4Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard)HIGH 7.10.3 %
CVE-2026-58314≤ 1.26.4Two SSRF findings in Gitea 1.26.2HIGH 7.70.4 %
CVE-2026-57897≤ 1.26.4Cross-Repo Information Disclosure via Org-Level Actions Run/Job APIsMEDIUM 6.50.4 %
CVE-2026-57894≤ 1.26.4Repository Migration Follows Git HTTP Redirects After URL Allow/Block Validation, Enabling Internal Git Repository ExfiltrationHIGH 8.50.4 %
CVE-2026-57886≤ 1.26.4Cross-repository issue/comment attachment re-linking can expose private attachment contentMEDIUM 5.90.3 %
CVE-2026-56755≤ 1.26.4Denial of Service (CPU & Memory Exhaustion) via O(N^2) String Concatenation in Debian Package UploadMEDIUM 6.20.2 %
CVE-2026-56750≤ 1.26.4Gitea Remember-Me Token Theft Not Invalidating Attacker SessionCRITICAL 9.10.5 %
CVE-2026-56657≤ 1.26.4Gitea SSH Key Parser Denial of ServiceMEDIUM 6.20.2 %
CVE-2026-56654≤ 1.26.4Privilege Escalation via Access Token Scope Escalation in APICRITICAL 9.80.8 %
CVE-2026-56443≤ 1.26.4Token public-only scope bypassed on Limited-visibility owners (Repository + Package categories) — residual after CVE-2026-25714 / PR #37118CRITICAL 9.60.5 %
CVE-2026-55987≤ 1.26.4OAuth2 sign-in reactivates an administrator-deactivated account on auth sources without refresh tokens (incomplete fix of #38009)HIGH 8.10.4 %
CVE-2026-55986≤ 1.26.4Email Management API Bypasses ManageCredentials Feature RestrictionsMEDIUM 5.40.3 %
CVE-2026-55984≤ 1.26.4Null Pointer Dereference in AddTime API Causes Authenticated Denial of ServiceLOW 2.70.5 %
CVE-2026-559821.26.2OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token ScopesCRITICAL 9.10.5 %
CVE-2026-54481≤ 1.26.4Internal API HTTP client hardcodes InsecureSkipVerify:true with no config override (CWE-295)HIGH 7.50.3 %
CVE-2026-50105≤ 1.26.4RSS/Atom feed handlers bypass API-token scope & public-only confinement (incomplete fix of #37698)MEDIUM 4.30.4 %
CVE-2026-42931≤ 1.24Denial of Service via Unbounded io.ReadAll in NPM Package Tag EndpointMEDIUM 6.50.5 %
CVE-2026-23603≤ 1.26.4Blind SSRF in OAuth2 avatar synchronization via unvalidated OIDC picture claimLOW 3.10.3 %
CVE-2026-584261.22.0 – 1.26.1Gitea Actions Artifacts V4 signed URL HMAC ambiguity allows cross-repository artifact read and cross-task upload-state writeCRITICAL 9.60.2 %
CVE-2026-58424≤ 1.26.2Permanent Fork PR Workflow Approval Gate BypassHIGH 8.90.3 %
CVE-2026-584231.23.0 – 1.26.2LFS authentication bypass via malformed SSH sub-verb allows unauthorized read access to private repositoriesHIGH 7.70.4 %
CVE-2026-58422≤ 1.26.1Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accountsCRITICAL 9.80.4 %
CVE-2026-58421< 1.26.2Unauthenticated ReDoS via CODEOWNERS pattern matching allows denial of serviceHIGH 7.50.4 %
CVE-2026-584191.26.2Notification API leaks private issue metadata after access revocationHIGH 7.50.4 %
CVE-2026-58418≤ 1.25.4SSRF via HTTP Redirect in Repository MigrationMEDIUM 6.50.3 %
CVE-2026-28744≤ 1.26.1Gitea Git smart HTTP bypasses repository token scopes for bearer tokensHIGH 8.10.4 %
CVE-2026-28740≤ 1.26.2Gitea LFS object reuse bypasses Code-unit authorizationHIGH 7.10.3 %
CVE-2026-287371.25.0 – < 1.26.0Gitea 3D file viewer allows stored XSS through glTF extensionsRequiredHIGH 8.70.4 %
CVE-2026-28705< 1.25.5Gitea repository dumps write release assets using unsafe path namesMEDIUM 5.30.5 %
CVE-2026-28699≤ 1.26.1Gitea Basic Auth bypasses OAuth2 access token scopesHIGH 8.10.6 %
CVE-2026-27783≤ 1.26.1Gitea issue-template APIs bypass repository unit authorizationMEDIUM 4.30.4 %
CVE-2026-27780< 1.26.0Gitea pre-receive hook can miss branch-protection checks after scanner errorsCRITICAL 9.80.6 %
CVE-2026-27779< 1.25.5Gitea forwarded-proto handling allows public URL spoofingHIGH 7.50.6 %
CVE-2026-277751.25.5Gitea pre-receive hook permission cache allows full repository write accessHIGH 8.80.9 %
CVE-2026-27771≤ 1.26.1Gitea Composer package source links use insufficient permission checksHIGH 8.21.4 %
CVE-2026-27761≤ 1.26.2Gitea repository feeds bypass API token scope enforcementMEDIUM 4.30.5 %
CVE-2026-27660< 1.25.5Gitea draft releases use insufficient permission checksHIGH 7.50.5 %
CVE-2026-27657< 1.25.5Gitea email settings allow changing another user's primary email addressHIGH 7.50.5 %
CVE-2026-26307< 1.25.5Gitea git grep search lacks a timeoutHIGH 7.50.6 %
CVE-2026-26292< 1.25.5Gitea LFS mirror synchronization bypasses migration HTTP transport restrictionsCRITICAL 9.80.7 %
CVE-2026-26247< 1.25.5Gitea OAuth2 PKCE S256 challenges are not enforced during token exchangeCRITICAL 9.10.5 %
CVE-2026-26232< 1.25.5Gitea OAuth2 authorization codes lack expiry and reuse enforcementCRITICAL 9.10.5 %
CVE-2026-26231≤ 1.26.1Gitea maintainer-edit permissions allow unauthorized commits to readable repositoriesHIGH 8.50.4 %
CVE-2026-25782< 1.25.5Gitea tracked-time deletion can target entries from another issueMEDIUM 5.30.4 %
CVE-2026-25779≤ 1.25.4Gitea redirect handling permits open redirects through backslash pathsMEDIUM 6.10.3 %
CVE-2026-25718< 1.25.5Gitea template repository generation mishandles symlinked pathsCRITICAL 9.10.6 %
CVE-2026-25714≤ 1.26.1Gitea user organization API bypasses public-only token filteringMEDIUM 4.30.4 %
CVE-2026-25712< 1.25.5Gitea organization permission APIs expose private visibility informationHIGH 7.50.5 %
CVE-2026-250381.26.2Gitea private organization labels are visible to unauthorized usersHIGH 7.50.6 %
CVE-2026-24690< 1.25.5Gitea pull-request branch updates use insufficient permission checksHIGH 7.50.5 %
CVE-2026-244511.26.2Gitea fork synchronization can expose private parent repository dataHIGH 7.50.4 %
CVE-2026-22874≤ 1.26.2Gitea webhook and migration allow-list filtering permits SSRFCRITICAL 9.60.5 %
CVE-2026-22555< 1.26.0Gitea organization forks can expose organization secrets without create permissionHIGH 8.10.4 %
CVE-2026-22547< 1.25.5Gitea repository creation accepts invalid field valuesCRITICAL 9.10.5 %
CVE-2026-20909< 1.25.5Gitea tracked-time list endpoint has insufficient permission checksMEDIUM 5.30.4 %
CVE-2026-20896≤ 1.26.2Gitea Docker image trusts spoofable reverse-proxy headers by defaultCRITICAL 9.82.8 %
CVE-2026-207791.5.0 – < 1.26.3Gitea TOTP single-use enforcement defect allows OTP replayHIGH 7.10.5 %
CVE-2026-20706≤ 1.26.1Gitea repository archive downloads bypass token scope checksCRITICAL 9.10.6 %
CVE-2026-20912≤ 1.25.3Gitea: Cross-Repository Authorization Bypass via Release Attachment Linking Leads to Private Attachment DisclosureCRITICAL 9.10.5 %
CVE-2026-20904≤ 1.25.3Gitea: Broken access control in OpenID visibility toggle enables cross-user visibility changesMEDIUM 6.50.3 %
CVE-2026-20897≤ 1.25.3Gitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)CRITICAL 9.10.5 %
CVE-2026-20888≤ 1.25.3Gitea Pull Requests Auto-Merge: Read-Only Users Can Cancel Scheduled Auto-Merge via Web Endpoint (Authorization Bypass)MEDIUM 4.30.3 %
CVE-2026-20883≤ 1.25.3Gitea Stopwatch API Missing Authorization Check Leads to Post-Revocation Information DisclosureMEDIUM 6.50.4 %
CVE-2026-20800≤ 1.25.3Notification API Leaks Private Repository Issue Titles After Collaborator Permission RevocationMEDIUM 6.50.4 %
CVE-2026-20750≤ 1.25.3Gitea Organization Projects Cross-Organization Authorization Bypass via Project ID (IDOR)CRITICAL 9.10.4 %
CVE-2026-20736≤ 1.25.3Gitea Web Attachment Deletion: Cross-Repository Unauthorized Deletion via Missing Repo Ownership CheckHIGH 7.50.4 %
CVE-2026-0798≤ 1.25.3Gitea Release Email Notifications Leak Private Repository Release Details After Access RevocationLOW 3.50.3 %
CVE-2024-68861.22.0Inproper Sanitation of field leading to stored XSSCRITICAL 10.033 %