Distro News

Gitea 28.4 patches critical RCE, password hash exposure, and 2FA bypass vulnerabilities

Key Takeaway

Gitea 28.4 fixes multiple high-severity security flaws including a repository initialization race condition enabling remote code execution, an information disclosure bug exposing password hashes since version 28.0, and an unlimited TOTP guessing weakness that could bypass two-factor authentication.

Summary

Gitea, the widely deployed self-hosted Git service, has released version 28.4 with urgent security fixes that the development team strongly recommends all users apply immediately. The most severe vulnerability, CVE-2026-125423, allows a user with repository creation privileges to exploit a race condition during initialization to overwrite Git hooks and execute arbitrary commands as the Gitea system account. Another critical flaw, CVE-2026-123006, has existed since Gitea 28.0 and causes the repository search endpoint to leak internal user data including password hashes, salts, and email addresses to authenticated users.

The release also hardens authentication by implementing a 15-minute lockout after five failed TOTP attempts, closing a vector for 2FA bypass when an attacker already knows the account password. Additional security work covers XSS prevention in issue reference previews, branch protection bypasses via specially crafted filenames, Actions secret exposure after workflow repository transfers, and multiple authorization gaps affecting OAuth2 tokens, pull request data, repository attachments, and Git LFS objects. Beyond security, Gitea 28.4 improves Actions reliability, fixes repository handling race conditions and deadlocks, updates OCI container image name compliance, enhances audit logging, and refreshes its Docker base to address a Go standard library HTTP vulnerability.

Security fixes and hardening in Gitea 28.4

  • Remote code execution via race condition (CVE-2026-125423): A user permitted to create repositories could exploit a race during repository initialization to overwrite a Git hook, achieving command execution with Gitea system account privileges.
  • Password hash disclosure via search endpoint (CVE-2026-123006): Since Gitea 28.0, the repository search endpoint returned internal user information including password hashes, salts, and email addresses; 28.4 restricts responses to commit status data only.
  • TOTP brute-force protection: Previously unlimited TOTP guesses allowed 2FA bypass when the account password was known; five failed attempts now trigger a 15-minute lockout on the affected account.
  • Actions and repository security gaps: Fixed XSS in issue reference previews, branch protection bypass via special characters in filenames, secret/token exposure after workflow repository transfers, and unauthorized access to attachments and Git LFS objects.
  • Build and dependency updates: Prebuilt binaries now use Go 1.27.4 to address an HTTP server vulnerability in the Go standard library, and Docker images refresh Alpine Linux base packages.

Why it matters

Self-hosted Git infrastructure represents a critical attack surface for open-source projects, enterprises, and individual developers who rely on Gitea as a lightweight alternative to GitHub or GitLab. The severity and breadth of these vulnerabilities, particularly the RCE and credential exposure flaws, make rapid patching essential for any organization running Gitea 28.x in production. The TOTP hardening and audit logging improvements also raise the baseline security posture for teams managing sensitive codebases and CI/CD secrets through Gitea Actions.

What to do

  • Upgrade to Gitea 28.4 immediately, as the developers strongly recommend this for all users.
  • Watch for 15-minute TOTP lockouts after five failed attempts, which now protects against 2FA bypass attempts.

Original reference: linuxiac.com →