CVE-2026-129525 | | | 2026-11-15 | Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. A user who can read a repository's issues bu… |
CVE-2026-129341 | | | 2026-11-15 | The web endpoint that removes an attachment skipped the permission check when the request came from the user who had uploaded the attachment, and it was reacha… |
CVE-2026-129337 | | | 2026-11-15 | Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforc… |
CVE-2026-128365 | | | 2026-11-15 | Removing a team's review request looked up a review by the negated team ID, which for the team with ID 2 is the ID of the built-in Actions user, and marked the… |
CVE-2026-128359 | | | 2026-11-15 | When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account… |
CVE-2026-127958 | | | 2026-11-15 | A pull request review created through the API as a draft (`event` set to `PENDING` or left empty) was added to the pull request timeline and announced through… |
CVE-2026-126338 | | | 2026-11-15 | Replying to a code review comment accepted a review ID that belongs to a different pull request, through the web form, the API and incoming mail replies. A sig… |
CVE-2026-125617 | | | 2026-11-15 | `GET /api/v1/users/{username}/orgs/{org}/permissions` only checked that the organization is visible to the caller and then returned the named user's role in it… |
CVE-2026-123642 | | | 2026-11-15 | The AGit flow (pushing to `refs/for/...`) did not check the pusher's access to pull requests again when it created the pull request. A user or deploy key with… |
CVE-2026-123638 | | | 2026-11-15 | The "Protected file patterns" setting of a branch protection rule was checked against file names as git prints them, and git quotes names that contain a double… |
CVE-2026-123065 | | | 2026-11-15 | When a release was edited, the files of the attachments to remove were deleted by the identifiers submitted in the form rather than by the attachments verified… |
CVE-2026-123009 | | | 2026-11-15 | When a file is edited in a fork through the web editor, Gitea can first copy a branch from the base repository into the fork. That copy did not check whether t… |
CVE-2026-123002 | | | 2026-11-15 | Gitea accepted an unlimited number of wrong TOTP passcodes during sign-in, in the password reset flow and for Basic authentication with the `X-Gitea-OTP` heade… |
CVE-2026-120991 | | | 2026-11-15 | When a container blob upload was rejected, for example because it exceeded a package size quota, the cleanup removed the blob from storage even if the same con… |
CVE-2026-120729 | | | 2026-11-15 | The popup shown when hovering an issue reference loaded its data from the path of the hovered link and inserted part of the response as HTML. A user who can po… |
CVE-2026-120725 | | | 2026-11-15 | With `REQUIRE_SIGNIN_VIEW = true`, the Git LFS endpoints still answered unauthenticated requests for repositories that are not private. An anonymous client who… |
CVE-2026-118535 | | | 2026-11-15 | A repository registered by its owner as a source of scoped workflows kept that registration when it was transferred to another owner. The new owner could then… |
CVE-2026-118389 | | | 2026-11-15 | The RubyGems package registry accepted gems whose platform, dependency names or dependency version requirements contain newline characters. Because the compact… |
CVE-2026-125423 | | | 2026-11-15 | A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repo… |
CVE-2026-123006 | | | 2026-11-15 | The repository search used by the dashboard (`GET /repo/search`) returned the internal commit status object of each repository. Since 28.0.0 that object includ… |
CVE-2026-120263 | Critical | 9.8 | 2026-11-01 | When `[oauth2_client].ACCOUNT_LINKING` is set to `auto` (not the default) and registration is enabled, the link-account sign-up form looked up the existing acc… |
CVE-2026-119627 | Medium | 4.3 | 2026-11-01 | The web profile and RSS/Atom feed routes of users and organizations checked only whether a signed-in viewer could see a limited-visibility owner, without consi… |
CVE-2026-119625 | Medium | 4.3 | 2026-11-01 | The `/{username}` web route accepted personal access tokens over HTTP Basic authentication without checking their scope. A token confined to an unrelated scope… |
CVE-2026-119533 | High | 7.5 | 2026-11-01 | Repository and organization project boards listed the pull requests that reference each issue on the board without checking whether the viewer can read them. W… |
CVE-2026-119441 | High | 7.5 | 2026-11-01 | `DELETE /api/v1/orgs/{org}/repos` deletes all repositories of an organization, but it did not enforce the public-only restriction of access tokens: the route o… |
CVE-2026-118504 | Medium | 6.5 | 2026-11-01 | The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository… |
CVE-2026-118395 | High | 7.5 | 2026-11-01 | Gitea 1.27.3 stopped personal access tokens restricted to public resources (`public-only`) from creating repositories through `POST /api/v1/user/repos` and `PO… |
CVE-2026-118394 | Medium | 4.3 | 2026-11-01 | The OAuth2 userinfo endpoint (`/login/oauth/userinfo`) decided whether to limit the `groups` claim to public organizations by re-parsing the `Authorization` he… |
CVE-2026-118386 | Medium | 6.5 | 2026-11-01 | Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the revie… |
CVE-2026-117685 | Critical | 9.1 | 2026-11-01 | The OCI registry's cross-repository blob mount checked the target package against the token's `public-only` restriction, but checked the source blob only again… |
CVE-2026-117677 | Medium | 6.5 | 2026-11-01 | When parsing an uploaded Helm chart, Gitea decompressed the archive and read every tar entry while looking for `Chart.yaml` without limiting the decompressed s… |
CVE-2026-117649 | Low | 3.5 | 2026-11-01 | The issue timeline API and the web issue page hid cross-reference events that point at issues the reader cannot access, but not "dependency added" and "depende… |
CVE-2026-117646 | Medium | 4.3 | 2026-11-01 | The repositories, stars and watching tabs of user profiles and the repository list of organization home pages included private repositories for every signed-in… |
CVE-2026-117635 | Medium | 6.5 | 2026-11-01 | The `/api/v1/admin` route group did not enforce the `public-only` restriction of personal access tokens. A public-only token with admin scope issued by a site… |
CVE-2026-116474 | Medium | 6.5 | 2026-11-01 | The `GITEA_TOKEN` of a Gitea Actions job authenticates as the `gitea-actions` system user, and the `/api/v1/user` email and GPG key endpoints accepted that use… |
CVE-2026-116296 | Medium | 6.5 | 2026-11-01 | The API routes for releases, release assets, milestones and repository labels did not reject changes to archived repositories. A user with write access to an a… |
CVE-2026-116289 | Critical | 9.1 | 2026-11-01 | Gitea did not reject personal access tokens restricted to public resources (`public-only`) on the organization Actions runner registration-token endpoint, and… |
CVE-2026-114199 | Medium | 5.3 | 2026-11-01 | `GET /api/v1/users/{username}/heatmap` computed the contribution heatmap with the repository access of the token owner and ignored the public-only restriction… |
CVE-2026-113429 | Medium | 5.4 | 2026-11-01 | Legacy (v1 to v3) Actions artifact uploads stored the request's `Content-Encoding` header unchecked in the column that is served as the artifact's `Content-Typ… |
CVE-2026-112887 | Medium | 4.3 | 2026-11-01 | Gitea Actions task tokens authenticate to the REST API as a shared system user with a negative ID, which repository, organization, project and key filters trea… |
CVE-2026-97859 | Medium | 6.5 | 2026-10-18 | Seven Gitea API routes under `/api/v1/users/{username}` (followers, following, following/{target}, starred, subscriptions, keys and gpg_keys) were registered w… |
CVE-2026-97204 | Low | 3.1 | 2026-10-18 | Deleting a label compared the ID of the repository in the request against the organization ID of organization labels, and the two ID sequences overlap. A user… |
CVE-2026-110494 | Medium | 6.3 | 2026-10-18 | Adding attachments to a release checked the repository and release of an attachment but not whether it was already linked to an issue or comment. A user with w… |
CVE-2026-110324 | Medium | 6.5 | 2026-10-18 | The visibility check of Gitea user profiles was applied to GET requests only, while `POST /{username}` (follow and unfollow) required only a signed-in user. An… |
CVE-2026-110311 | Medium | 4.3 | 2026-10-18 | Creating a draft release through the API returned an `assets` list that was built from a release without an ID, which matched every attachment that was not lin… |
CVE-2026-109844 | Medium | 4.3 | 2026-10-18 | `GET /api/v1/user/subscriptions` returned the metadata of every repository a user was watching without checking that the user still had access to it. A user wh… |
CVE-2026-109553 | High | 7.5 | 2026-10-18 | Gitea resolved the principals of an SSH certificate by searching the content of all stored public keys instead of only principal keys. When Gitea trusts a user… |
CVE-2026-107686 | Medium | 4.3 | 2026-10-18 | The Gitea web handlers for adding and removing reactions on issues and comments did not refuse locked issues for users without write access, although the API d… |
CVE-2026-107618 | High | 8.1 | 2026-10-18 | `POST /{owner}/{repo}/topics` was registered without the sign-in middleware that provides the cross-origin protection, so a request issued by a third-party sit… |
CVE-2026-105964 | Medium | 6.5 | 2026-10-18 | The Gitea Actions artifact v4 (Twirp) handlers read the whole request body into memory without a size limit. A user who can run a workflow and obtains the runn… |
CVE-2026-105661 | Medium | 5.3 | 2026-10-18 | Requesting `/{username}/-/repositories` for an individual user instead of an organization made the organization home handler dereference a nil organization and… |
CVE-2026-104627 | Medium | 5.4 | 2026-10-18 | The Gitea OpenID association callback in the security settings accepted a positive OpenID 2.0 assertion without checking that the signed-in user had started th… |
CVE-2026-78433 | Medium | 5.9 | 2026-10-14 | Gitea's web attachment handler skips its cross-repository ownership check for attachments created before 16 January 2026 and checks permissions against the rep… |
CVE-2026-78231 | Medium | 5.3 | 2026-10-14 | When OpenID sign-in is enabled, Gitea processes unauthenticated assertion parameters and sends an HTTP POST request to the caller-supplied OpenID provider endp… |
CVE-2026-73814 | Medium | 6.5 | 2026-10-14 | Gitea's collaboration access-mode endpoint accepts the Owner access mode from an authenticated repository collaborator with Admin access. The collaborator can… |
CVE-2026-73804 | High | 8.1 | 2026-10-14 | Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account. API requests signed with the corresp… |
CVE-2026-73802 | High | 8.8 | 2026-10-14 | Gitea Runner passes workflow-controlled container options into Docker job container configuration while privileged mode is disabled. Host namespace settings, e… |
CVE-2026-73800 | High | 8.8 | 2026-10-14 | Gitea resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pull_request_target event. A fork author… |
CVE-2026-73539 | High | 7.5 | 2026-10-14 | Gitea substitutes a URL derived from the markup Context field into external renderer command templates without escaping the reference path before shell-style a… |
CVE-2026-73535 | High | 8.8 | 2026-10-14 | Gitea's OpenID connect handler accepts a user's password without enforcing enrolled TOTP or WebAuthn verification before completing sign-in and linking an Open… |
CVE-2026-73273 | Medium | 4.3 | 2026-10-14 | Gitea's Maven upload handler reads checksum uploads entirely into memory and returns before enforcing package-size quotas. An authenticated user with package-p… |
CVE-2026-73135 | Medium | 5.3 | 2026-10-14 | Gitea uses inconsistent repository visibility predicates, and the condition used by some repository-listing endpoints admits repositories whose owners are hidd… |
CVE-2026-73130 | Medium | 4.3 | 2026-10-14 | Gitea does not limit the length of the gitignores field accepted by repository-creation forms and the API. Repository initialization splits the field into temp… |
CVE-2026-73126 | Medium | 4.3 | 2026-10-14 | Gitea's Actions workflow status badge endpoint does not enforce repository-read scope or the public-only restriction on the token authenticating the request. A… |
CVE-2026-71301 | Medium | 4.3 | 2026-10-14 | Gitea's repository markup endpoint resolves same-repository pull request references without enforcing the viewer's Pull Requests permission. A member with only… |
CVE-2026-71184 | High | 8.8 | 2026-10-14 | Gitea's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the ru… |
CVE-2026-70407 | Medium | 4.3 | 2026-10-14 | Gitea's organization-list API does not enforce the read:organization token scope. A token limited to another category, such as read:misc, can retrieve organiza… |
CVE-2026-70406 | Medium | 6.5 | 2026-10-14 | Gitea's shared comparison helper omits the token repository-access check used when updating pull requests. A public-only token with read:repository scope can r… |
CVE-2026-70402 | Medium | 5.8 | 2026-10-14 | Gitea creates server-side Git hook directories and scripts with mode 0777 and relies on the process umask to restrict access. With a permissive umask such as 0… |
CVE-2026-70400 | Medium | 5.4 | 2026-10-14 | Gitea's repository migration API accepts a public-only token when the request specifies creation of a private repository. A delegated token intended to operate… |
CVE-2026-70396 | Medium | 5.4 | 2026-10-14 | Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation route… |
CVE-2026-68964 | Medium | 4.3 | 2026-10-14 | Gitea's user SSH and GPG key-list API endpoints omit the profile visibility check applied by their web equivalents. A restricted account can retrieve public ke… |
CVE-2026-68957 | Medium | 4.3 | 2026-10-14 | Gitea's API and web issue-search paths do not treat restricted accounts as anonymous viewers when evaluating Limited-visibility repository owners. A restricted… |
CVE-2026-67577 | Medium | 4.3 | 2026-10-14 | Gitea's activity-feed and contribution-heatmap API handlers do not apply the profile visibility check for restricted accounts viewing Limited-visibility users… |
CVE-2026-66877 | High | 8.1 | 2026-10-14 | Gitea enforces first-time fork contributor approval by blocking jobs, but some job transition and dispatch paths do not re-check the run's approval requirement… |
CVE-2026-66874 | Medium | 6.5 | 2026-10-14 | For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped status when workflow branch or path filters… |
CVE-2026-66853 | Medium | 4.3 | 2026-10-14 | Gitea's user organization-list API includes Limited-visibility organizations for authenticated restricted accounts without applying the visibility restriction… |
CVE-2026-66849 | Medium | 4.3 | 2026-10-14 | Gitea's package registry grants authenticated users read access to packages owned by Limited-visibility users without excluding restricted accounts. A restrict… |
CVE-2026-63792 | Medium | 5.3 | 2026-10-14 | Gitea's collaborative-owner authorization path for reading cross-repository reusable workflows does not exclude fork pull request runs. An approved fork workfl… |
CVE-2026-63021 | Medium | 6.5 | 2026-10-14 | Gitea's Swift package parser limits each manifest to 128 KiB but does not limit the number of manifests or their aggregate size before reading them into memory… |
CVE-2026-62925 | Medium | 6.5 | 2026-10-14 | Gitea parses Alpine package uploads before enforcing package-size quotas and does not bound the decompressed .PKGINFO data or its dependency and provides entry… |
CVE-2026-60021 | Medium | 6.5 | 2026-10-14 | Gitea's initial GitLab migration version probe uses an HTTP client without a timeout and does not attach the migration task's cancellation context. An authenti… |
CVE-2026-60018 | Medium | 6.5 | 2026-10-14 | Gitea's OneDev migration downloader reads the entire remote version response into memory without a size limit and uses a client without a timeout. An authentic… |
CVE-2026-60010 | Medium | 6.5 | 2026-10-14 | Gitea's repository-side team-link API allows a repository administrator who is not an organization owner to attach organization teams to a repository despite R… |
CVE-2026-60008 | Low | 3.5 | 2026-10-14 | Gitea's Jupyter notebook renderer inserts the notebook's language_info.name metadata into a CSS class attribute while disabling sanitization and rendering dire… |
CVE-2026-59774 | Critical | 9.8 | 2026-10-14 | Gitea's Org-mode markup renderer processes INCLUDE directives supplied to the repository markup endpoint without preventing access to server-side files. An una… |
CVE-2026-59766 | Medium | 4.3 | 2026-10-14 | Gitea's starred-repository and tracked-time API endpoints do not re-check current repository permissions before returning data associated with the requesting u… |
CVE-2026-25946 | Medium | 5.3 | 2026-10-14 | When OpenID sign-in is enabled, Gitea accepts a user-supplied OpenID URL and performs discovery requests without validating the destination against internal ne… |
CVE-2026-97626 | Medium | 4.3 | 2026-10-06 | Requesting a user or organization profile page (`GET /{username}`) with an `Accept: application/rss+xml` or `Accept: application/atom+xml` header returned the… |
CVE-2026-97208 | Medium | 4.9 | 2026-10-06 | The Gitea API endpoint for creating push mirrors (`POST /api/v1/repos/{owner}/{repo}/push_mirrors`) checked only whether mirroring was enabled and not the `[mi… |
CVE-2026-96594 | Medium | 6.1 | 2026-10-06 | The Gitea API endpoint `GET /api/v1/repos/{owner}/{repo}/media/{filepath}` wrote files of up to 1 KiB that are stored directly in Git, not in LFS, to the respo… |
CVE-2026-89182 | Medium | 5.4 | 2026-10-06 | With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push opti… |
CVE-2026-86684 | High | 7.1 | 2026-10-06 | The Gitea push mirror API checked whether the repository owner, instead of the requesting user, may use local file system paths. On instances with `[security]… |
CVE-2026-105268 | Medium | 4.3 | 2026-10-06 | The Gitea API routes for issue attachments (`/api/v1/repos/{owner}/{repo}/issues/{index}/assets/{attachment_id}`) also accepted attachments that belong to comm… |
CVE-2026-105267 | High | 8.1 | 2026-10-06 | The Gitea web route for deleting tags (`POST /{owner}/{repo}/tags/delete`) requires only write access to the Code unit, but shares its handler with release del… |
CVE-2026-104633 | Medium | 6.5 | 2026-10-06 | When migrating a repository from another Gitea instance, Gitea used the page size reported in the source server's API settings to end its paginated downloads… |
CVE-2026-101023 | Critical | 9.1 | 2026-10-06 | Gitea's OAuth2 token endpoint verified the signature and grant of a token submitted with the `refresh_token` grant type, but not that the token was a refresh t… |
CVE-2026-96589 | Medium | 4.3 | 2026-10-06 | When a private repository is transferred to a user who lacks access, Gitea grants that recipient temporary read access as a collaborator so they can review the… |
CVE-2026-96580 | High | 7.5 | 2026-10-06 | Gitea expanded a workflow's static `strategy.matrix` into its full Cartesian product without a size limit when creating a run, before the fork pull request app… |
CVE-2026-96404 | High | 8.1 | 2026-10-06 | When Gitea's web installer is reachable against a database that already contains users, such as after `INSTALL_LOCK` has been reset to `false`, submitting the… |