Gitea 28.4 Patches Multiple Security Vulnerabilities

Gitea 28.4 addresses security vulnerabilities involving remote code execution, password hash exposure, authentication, and repository permissions.

Gitea, the self-hosted Git service and software development platform, has released version 28.4, the fourth maintenance update in the 28.x series. Given the severity of the security fixes, the developers strongly recommend that all users upgrade as soon as possible.

One of the most serious vulnerabilities, tracked as CVE-2026-125423, affects repository initialization. Under certain conditions, a user allowed to create repositories could exploit a race condition to overwrite a Git hook on the server and execute commands with the privileges of the Gitea system account.

Another significant issue, CVE-2026-123006, involves the repository search endpoint. Since Gitea 28.0, its responses could include internal user information, allowing authenticated users to retrieve repository owners’ password hashes, salts, and email addresses. The endpoint now limits returned data to the necessary commit status information.

Authentication security has also been strengthened. Previously, Gitea allowed unlimited attempts to guess time-based one-time passwords, potentially enabling attackers who knew an account password to bypass two-factor authentication. With version 28.4, five failed attempts trigger a 15-minute lockout for further TOTP attempts on the affected account.

The update also fixes a cross-site scripting vulnerability involving issue reference previews, a branch protection bypass affecting filenames with special characters, and an Actions security issue that could expose secrets and tokens after workflow repository transfers.

Other fixes prevent deactivated users from obtaining fresh OAuth2 or OpenID Connect tokens, close permission checks that could expose pull request data, and fix unauthorized access to repository attachments and Git LFS objects.

Apart from these security changes, Gitea 28.4 introduces several reliability improvements. In Actions, job conditions now correctly account for dependent jobs completed during the same evaluation pass. The Actions API properly recognizes repository administrator permissions.

Repository handling has also been improved. A bug that could roll back branches when Git post-receive hooks arrived out of order has been fixed. Deadlocks during concurrent updates to repository language statistics have also been resolved.

Additionally, the release corrects how team administrator permissions are applied and prevents pull mirror credentials from being reused when changing the destination host.

For package management, Gitea now accepts container image names permitted by OCI 1.1. Auditing improvements ensure changes to repository webhooks, branch protection rules, deploy keys, and push mirrors are properly recorded.

Finally, the update fixes several issues involving pull requests, notifications, and API responses, refreshes dependencies, and updates the Alpine Linux base packages used in Gitea’s Docker images. Prebuilt binaries are now compiled with Go 1.27.4, addressing an HTTP server vulnerability in the Go standard library.

For more information, see the official announcement.

Bobby Borisov

Bobby Borisov

Bobby, an editor-in-chief at Linuxiac, is a Linux professional with over 20 years of experience. With a strong focus on Linux and open-source software, he has worked as a Senior Linux System Administrator, Software Developer, and DevOps Engineer for small and large multinational companies.

Leave a Reply

Your email address will not be published. Required fields are marked *