Repository creation race
Users allowed to create and push to repositories can race auto-initialization and overwrite a server hook via a symlink.
Gitea 28.4.0 fixes a repository creation race that can lead to command execution as the service account, and a dashboard search that exposed repository owners’ password hash material to signed-in users.
The initialization race, CVE-2026-125423, needs repository creation and push rights, automatic initialization with the default README, and a server layout where a crafted symlink can resolve to a writable Git hook. Successful execution has the operating system permissions of the Gitea service. The advisory documents reproduction on 28.3.0, 28.2.0, 1.27.1 and 1.25.5. Turning off user-defined Git hooks alone does not close this path.
The repository search leak, CVE-2026-123006, affects 28.0.0 through 28.3.0. Access requires a signed-in account and a visible repository with a commit status. The advisory demonstrates the exposure through public repositories with a commit status. The material includes hashes, salts, and primary email addresses and can support offline password guessing. The source does not establish which accounts, if any, were targeted.
The official upgrade documentation covers deployment-specific steps. If you suspect service account command execution, preserve evidence, isolate the affected instance, and rotate exposed credentials from a trusted system before restoring service.
The 28.4.0 binaries also use Go 1.27.4 for the HTTP server fix already covered in the Go November advisory. Some Gitea fixes shipped earlier. The RubyGems index fix first shipped in 28.3.0, and parts of the issue and pull request authorization fix shipped in 28.2.0 and 28.3.0. Upgrade to the full release to pick up the remaining fixes.
Users allowed to create and push to repositories can race auto-initialization and overwrite a server hook via a symlink.
A signed-in user can obtain password hash material and email addresses of owners of visible repositories with a commit status.
Someone with release write access can delete another attachment's stored file if they know its UUID.
A writer can bypass protected file patterns because Gitea matched names against Git's quoted output.
A signed-in user with a review ID can copy diff context from a repository they cannot read.
A crafted issue reference to attacker-controlled content can run script when another user hovers over it.
After a repository registered as an owner-scoped workflow source is transferred, the new owner can modify workflows that still run with the former owner's repository secrets and token.
An attacker who already knows an account password can repeatedly guess its six-digit TOTP.
A user with an existing fork can copy a base branch through the web editor after losing upstream read permission.
A registry publisher can use newlines in gem metadata to inject index entries. This fix first shipped in 28.3.0.
Shared routes could expose issue or pull request data to users with only the other permission. Earlier releases covered some API routes.
In the organization that owns team ID 2, a user who can change review requests can make an Actions approval count toward required approvals.
A user with read access can push over HTTP before a migration, fork or template-created repository has its hooks.
A previous uploader with sufficient read access can delete the asset after losing write rights.
On instances enforcing a package quota, a rejected upload can delete blobs shared with other packages when the uploader has matching bytes.
A user or deploy key with code read access or wiki write access can open a pull request through AGit without pull request access.
A signed-in user can look up another user's role in a public or limited organization.
When Gitea is an OAuth2 or OIDC provider, an existing refresh token or unused authorization code can yield new tokens after account deactivation.
Git LFS ignores required sign-in for non-private repositories if the requester knows the repository path and object SHA-256.
Draft reviews created through the API can appear in timelines and notifications before submission.
| Product | Safe from | Note |
|---|---|---|
| Gitea | 28.4.0 |
Nov 15, 2026
Gitea publishes 28.4.0 and its security advisories
The maintenance release closes the initialization race, restricts repository search output and repairs other access control and workflow issues.
We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.