Is Gitea 1.25.0 affected?

Vulnerabilities affecting 1.25.0

• 9.9
  CVE-2026-73802 gitea-runner: workflow container.options passes host namespaces and capability flags to job container when privileged mode is disabled fixed in 3.0.0
• 9.8
  CVE-2026-59774 Unauthenticated Arbitrary File Read can lead to RCE fixed in 1.27.1
• 9.8
  CVE-2026-20896 Gitea Docker image: `REVERSE_PROXY_TRUSTED_PROXIES = *` default lets any source IP impersonate any user via `X-WEBAUTH-USER`
• 9.6
  CVE-2026-58443 Public-only repository tokens can update private PR head branches
• 9.6
  CVE-2026-58426 Gitea Actions Artifacts V4 signed URL HMAC ambiguity allows cross-repository artifact read and cross-task upload-state write
• 9.6
  CVE-2026-22874 Incomplete SSRF Protection in Webhook and Migration Allow-list Default Filter
• 9.1
  CVE-2026-103059 Built-in SSH server auth bypass via case-insensitive LIKE key lookup
• 9.0
  CVE-2026-95106 Duplicate tree-entry name: Gitea renders the benign blob while checkout and CI run the malicious one
• 9.0
  CVE-2026-103667 Stored XSS in Gitea container registry via unvalidated blob Content-Type (mediaType injection)
• 9.0
  CVE-2026-104626 Cancelled fork-PR Actions jobs are revived by later approval
• 9.0
  CVE-2026-104632 Untrusted first-time fork PR achieves self-hosted Actions runner RCE without approval via cancel-then-rerun
• 8.9
  CVE-2026-58424 Permanent Fork PR Workflow Approval Gate Bypass
• 8.8
  CVE-2026-71184 Gitea Actions: fork pull request approval bypass via `pull_request_review_comment` (missing `WithPullRequest`)
• 8.8
  CVE-2026-73535 2FA bypass and persistent account takeover via OpenID identity linking
• 8.8
  CVE-2026-73800 Secret Exfiltration via Reusable Workflow Resolution in pull_request_target Events fixed in 1.27.2
• 8.7
  CVE-2026-94205 Gitea Actions: fork pull request approval bypass via maintainer-triggered pull_request sub-events (ifNeedApprovalWith keys on the event actor, not the pull request author)
• 8.7
  CVE-2026-66877 RCE on self-hosted runners | fork-PR approval gate (`NeedApproval`) bypass via job-level concurrency cancellation
• 8.7
  CVE-2026-28737 Stored XSS via glTF `extensionsRequired` in Gitea 3D File Viewer fixed in 1.26.0
• 8.5
  CVE-2026-96594 Stored XSS via Repository Media API
• 8.5
  CVE-2026-89430 Gitea Push Mirror Host Policy Bypass Enables SSRF and Forced Writes to Internal Git Repositories
• 8.5
  CVE-2026-101029 Migration / pull-mirror SSRF, egress allow-list bypass via multi-answer DNS - 3 findings
• 8.5
  CVE-2026-57894 Repository Migration Follows Git HTTP Redirects After URL Allow/Block Validation, Enabling Internal Git Repository Exfiltration fixed in 1.27.0
• 8.5
  CVE-2026-26231 Authorization Bypass via "Allow edits from maintainers" allows unauthorized commits to any readable repo
• 8.2
  CVE-2026-27771 Critical Vulnerability - Already emailed
• 8.1
  CVE-2026-104627 Cross-Session OpenID Credential Linking Enables Account Takeover
• 8.1
  CVE-2026-97208 Gitea push-mirror creation API does not enforce the site-wide DISABLE_NEW_PUSH policy
• 8.1
  CVE-2026-96404 Installer Re-run Against an Already-Populated Database Grants an Authenticated Session for an Existing Admin Account Without Password Verification
• 8.1
  CVE-2026-60010 Repo-side team-link endpoint still bypasses RepoAdminChangeTeamAccess
• 8.1
  CVE-2026-73278 WebAuthn second factor is bypassed on OAuth2/OpenID sign-in (WebAuthn-only users)
• 8.1
  CVE-2026-73804 User-scoped tokens can mint unscoped HTTP signature API credentials
• 8.1
  CVE-2026-58439 Branch Protection Bypass via PR Retargeting Preserves Stale `official` Approval Flag
• 8.1
  CVE-2026-55987 OAuth2 sign-in reactivates an administrator-deactivated account on auth sources without refresh tokens (incomplete fix of #38009)
• 8.1
  CVE-2026-24791 Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes
• 8.1
  CVE-2026-22555 API Fork Missing CanCreateOrgRepo Check Allows Org Secret Exfiltration fixed in 1.26.0
• 8.1
  CVE-2026-28699 OAuth2 access token scope enforcement bypass via HTTP Basic authentication
• 8.1
  CVE-2026-28744 Git Smart HTTP Skips Repository Token Scopes for Bearer Tokens
• 7.7
  CVE-2026-101027 SSRF via DNS rebinding: MatchHostOrIP short-circuits IP check when hostname matches ALLOWED_DOMAINS
• 7.7
  CVE-2026-70406 Public-only tokens can read private head repositories via compare and pull request creation (incomplete fix of CVE-2026-58443)
• 7.7
  CVE-2026-58423 LFS authentication bypass via malformed SSH sub-verb allows unauthorized read access to private repositories
• 7.6
  CVE-2026-58422 Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts
• 7.5
  CVE-2026-109553 VerifyCert maps SSH certificate principals onto other users' SSH public keys
• 7.5
  CVE-2026-73539 Remote Code Execution via unescaped markup `Context` into external renderer argv
• 7.5
  CVE-2026-54481 Internal API HTTP client hardcodes InsecureSkipVerify:true with no config override (CWE-295)
• 7.1
  CVE-2026-86684 Push-mirror API checks local-path permission on the repository owner instead of the caller
• 7.1
  CVE-2026-96399 Uncaught Exception and Out-of-bounds Read results in Gitea crash
• 7.1
  CVE-2026-58437 Repository Visibility Manipulation via Git Push Options
• 7.1
  CVE-2026-28740 Git LFS object reuse allows non-Code access to authorize private source objects
• 7.1
  CVE-2026-20779 TOTP TOCTOU race on web 2FA paths + missing replay check on Basic-Auth `X-Gitea-OTP` surface fixed in 1.26.3
• 6.8
  CVE-2026-58440 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`)
• 6.7
  CVE-2026-58420 Local File Inclusion via file:// URI in Migration Restore
• 6.5
  CVE-2026-110324 Private profile information leaks on POST request
• 6.5
  CVE-2026-105964 Gitea Actions Artifact V4 API: unbounded request body read in parseProtobufBody enables memory-exhaustion DoS
• 6.5
  CVE-2026-104633 A migration source reporting max_response_items: 0 makes six paginated loops in the Gitea downloader never terminate, exhausting server memory from one authenticated request
• 6.5
  CVE-2026-105267 POST /{owner}/{repo}/tags/delete requires only Code:Write but destroys Releases and their attachment blobs
• 6.5
  CVE-2026-60018 Authenticated DoS in OneDev migration via unbounded version response body fixed in 1.27.3
• 6.5
  CVE-2026-60021 Authenticated DoS in GitLab migration via uncancelable version probe fixed in 1.27.3
• 6.5
  CVE-2026-62925 Unbounded Alpine .PKGINFO parse amplifies a small .apk upload into process memory
• 6.5
  CVE-2026-63021 Swift registry per-file 128KiB manifest guard bypassed by aggregation
• 6.5
  CVE-2026-66874 A fork pull request author can satisfy a required Actions status check without any workflow running, because a filtered out workflow taken from the pull request HEAD posts a `skipped` commit status that counts as success
• 6.5
  CVE-2026-73814 Admin repository collaborator can self-escalate to Owner and transfer the repository
• 6.5
  CVE-2026-58428 Release attachment extension allowlist bypass via web release edit form (variant of CVE-2025-68939)
• 6.5
  CVE-2026-57897 Cross-Repo Information Disclosure via Org-Level Actions Run/Job APIs
• 6.5
  CVE-2026-58442 Repository migration SSRF via multi-answer DNS allow-list bypass
• 6.5
  CVE-2026-58418 SSRF via HTTP Redirect in Repository Migration
• 6.3
  CVE-2026-110494 Gitea AddReleaseAttachments missing IssueID check allows issue attachment metadata exposure and deletion via releases
• 6.3
  CVE-2026-63792 Fork pull requests can read reusable workflow files from another private repository (missed sibling of GHSA-fj8v-hjwv-qm88)
• 6.3
  CVE-2026-58416 Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard)
• 6.3
  CVE-2026-58441 SSRF in restore-repo via unsanitized pull_request.yml Head.CloneURL
• 5.9
  CVE-2026-58432 Missing Authorization and Authorization Bypass Through User-Controlled Key and Incorrect Permission Assignment for Critical Resource and Exposure of Sensitive Information to an Unauthorized Actor in code.gitea.io/gitea
• 5.9
  CVE-2026-57886 Cross-repository issue/comment attachment re-linking can expose private attachment content
• 5.8
  CVE-2026-70402 Permissive Git hook directory and script modes may allow local code execution as the Gitea service account
• 5.4
  CVE-2026-70396 Organization repository creation endpoint skips repository token scope
• 5.4
  CVE-2026-70400 Repository migration skips public-only token guard for private repository creation
• 5.4
  CVE-2026-55986 Email Management API Bypasses ManageCredentials Feature Restrictions
• 5.3
  CVE-2026-105661 Unauthenticated nil-pointer panic on /{username}/-/repositories for individual users
• 5.3
  CVE-2026-78231 Unauthenticated Blind SSRF via OpenID Sign-In Verification
• 5.3
  CVE-2026-73135 Repository listing exposes repositories owned by hidden users due to inconsistent visibility predicate
• 5.3
  CVE-2026-58507 Private Repository Existence Disclosure via go-get Meta Endpoint
• 5.1
  CVE-2026-25779 Open Redirect via redirect_to in Gitea
• 4.9
  CVE-2026-58429 Public-Only Personal access tokens scope bypass in Organization and Permission Endpoints
• 4.3
  CVE-2026-109844 Gitea watched-repos API (GET /api/v1/user/subscriptions) leaks private repository metadata after team permission downgrade
• 4.3
  CVE-2026-110311 Draft releases include attachment metadata from other repositories
• 4.3
  CVE-2026-107686 Locked issues and comments still accept reactions through the web UI
• 4.3
  CVE-2026-105268 Issue-scoped attachment routes accept comment-scoped attachment ids, letting an issue opener delete or rename other users' comment attachments
• 4.3
  CVE-2026-104636 Raw Git redirect SSRF bypass in push mirrors, WikiRemoteURL, and PR-head fetches
• 4.3
  CVE-2026-96400 Migration SSRF policy regression: ALLOWED_DOMAINS permits reserved addresses despite ALLOW_LOCALNETWORKS=false
• 4.3
  CVE-2026-96589 Incorrect Authorization in Repository Transfer Allows Persistent Unauthorized Read Access
• 4.3
  CVE-2026-73126 Gitea workflow badge bypasses API token scopes
• 4.3
  CVE-2026-73273 Package size quota bypass and unbounded memory read in the Maven checksum upload path
• 4.3
  CVE-2026-67577 Restricted users can access limited-visibility users' activity feeds and contribution heatmaps through the API
• 4.3
  CVE-2026-68964 Restricted users can read limited-visibility users’ SSH and GPG keys through the API
• 4.3
  CVE-2026-58425 OAuth token introspection returns metadata of tokens issued to other clients (RFC 7662 section 4 violation)
• 4.3
  CVE-2026-58431 Public-only API token restriction is not enforced on team API routes
• 4.3
  CVE-2026-56443 Token public-only scope bypassed on Limited-visibility owners (Repository + Package categories) — residual after CVE-2026-25714 / PR #37118
• 4.3
  CVE-2026-50105 RSS/Atom feed handlers bypass API-token scope & public-only confinement (incomplete fix of #37698)
• 4.3
  CVE-2026-27761 API access token scope enforcement bypass on repository RSS/Atom feed endpoints leaks private repository commit data
• 4.3
  CVE-2026-27783 Missing repository-unit authorization on issue-template API endpoints
• 4.3
  CVE-2026-25714 Incomplete CVE-2025-68941 fix: /user/orgs missing checkTokenPublicOnly + switch-case logic flaw
• 3.7
  GHSA-m984-2424-x6vw Generic attachment downloads bypass draft-release visibility checks
• 3.5
  CVE-2026-97204 DeleteLabel compares one untyped id against whichever namespace the label uses, letting a repo collaborator delete an ID-colliding organisation's labels
• 3.1
  CVE-2026-23603 Blind SSRF in OAuth2 avatar synchronization via unvalidated OIDC picture claim
• 2.7
  CVE-2026-58511 Webhook Authorization Header Returned in Plaintext via API
• 2.7
  CVE-2026-55984 Null Pointer Dereference in AddTime API Causes Authenticated Denial of Service
• 2.7
  CVE-2026-58445 Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API
• low
  CVE-2026-97859 API routes for user social graph, keys, and starred repos bypass private visibility check
• low
  CVE-2026-107618 Cross-Site Request Forgery on `POST /{owner}/{repo}/topics`
• medium
  CVE-2026-97626 Web RSS/Atom Accept-header bypass leaks activity feeds of limited/private users and orgs
• medium
  CVE-2026-101023 OAuth access tokens can be exchanged as refresh tokens
• medium
  CVE-2026-95112 Algorithmic Complexity DoS in Issue Reference Parsing
• medium
  CVE-2026-103504 API team demotion does not reset unit permissions
• medium
  CVE-2026-79960 Deploy keys impersonate the repository owner in the hook pipeline
• high
  CVE-2026-70357 Migration SSRF via DNS Rebinding — TOCTOU Between DNS Validation and Git Connection
• medium
  CVE-2026-96580 Uncontrolled resource consumption — unapproved fork-PR workflow with a large static strategy.matrix exhausts server memory at run-creation
• high
  CVE-2026-103670 Unapproved fork PR cancels trusted in-progress runs via run-level concurrency
• low
  GHSA-qg66-h68v-5x2h Arbitrary File Read via Path Traversal in gitea restore-repo
• medium
  CVE-2026-70407 Token Scope Bypass on `GET /api/v1/orgs`
• low
  CVE-2026-71301 Wiki-only members can read private pull request titles through markup preview
• low
  CVE-2026-73504 Unauthenticated artifact-to-repository oracle in raw Actions downloads
• medium
  CVE-2026-73130 Unbounded gitignores repository-creation field enables linear template-read amplification
• medium
  CVE-2026-66849 Package registry: restricted users can read packages of limited-visibility users (authorization bypass)
• low
  CVE-2026-66853 Restricted users can enumerate limited-visibility organizations via the user org-list API (authorization bypass)
• high
  CVE-2026-68957 Restricted users can read limited-visibility users' issue titles and bodies through issue search
• high
  CVE-2026-59765 SSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud Metadata
• medium
  CVE-2026-59763 Unbounded Arch package file metadata can cause resource amplification in Gitea package uploads
• medium
  CVE-2026-58508 Two SSRF vulnerabilities in Gitea migration/mirror (DNS rebinding + missing re-validation)
• medium
  CVE-2026-58510 GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private
• high
  CVE-2026-58314 Two SSRF findings in Gitea 1.26.2
• high
  CVE-2026-58436 ParseAcceptLanguage quadratic-time DoS via Locale middleware on unauthenticated requests
• medium
  CVE-2026-56755 Denial of Service (CPU & Memory Exhaustion) via O(N^2) String Concatenation in Debian Package Upload
• low
  CVE-2026-56750 Gitea Remember-Me Token Theft Not Invalidating Attacker Session
• medium
  CVE-2026-56657 Gitea SSH Key Parser Denial of Service
• medium
  CVE-2026-56654 Privilege Escalation via Access Token Scope Escalation in API
• high
  CVE-2026-58435 Gitea LFS Deploy-Key Privilege Escalation
• low
  CVE-2026-58417 REST API exposes organization membership of private organizations to public
• medium
  CVE-2026-58427 Private org member list leaked via /members API endpoint — incomplete fix for PR #38145
• medium
  CVE-2026-58438 Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access
• high
  CVE-2026-58433 Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting
• medium
  CVE-2026-58421 Unauthenticated ReDoS via CODEOWNERS pattern matching allows denial of service fixed in 1.26.2
• medium
  CVE-2026-20706 Token scope bypass on web archive download endpoint (variant of PR #37698)

Newer releases