Gitea 28.4.0, released on November 15, carries 21 CVE entries, 19 of them fixes to Gitea’s own code that ship for the first time, and the most serious in impact lets a signed-in user race repository auto-initialization, overwrite a server git hook and run commands as the Gitea system user. Every fix is merged and has a published GitHub advisory; neither the release post nor the advisories checked for this piece mention attacks in the wild.

Three fixes rated High

Command execution through a README symlink

CVE-2026-125423 is rated High at CVSS 8.5. As the GHSA-6m4f-m9vc-7946 advisory on the auto-init push race describes it, an attacker creates a repository with auto-init enabled and, before initialization finishes, pushes a tree in which README.md is a symlink to the server-side post-receive hook; Gitea’s README generation then writes the repository description through that symlink, and the rewritten hook runs when Gitea’s own initialization push triggers it. Any account that can create and push to a repository is enough, so instances that let strangers register carry the widest exposure. The advisory limits its own claim: success depends on timing and on a compatible filesystem layout, and it claims no unauthenticated path, no root access and no container escape. The fix, merged in PRs #40376 and #40383, builds the initial commit in a fresh directory and refuses pushes until a new repository is fully initialized.

Gitea 28.4 Fixes 19 Vulnerabilities In Its Own Code, Including An Authenticated Command-Execution Race In Repository Auto-Init

Password hashes in repository search

CVE-2026-123006 (CVSS 8.8) affects 28.0.0 through 28.3.0 only. The /repo/search endpoint serialized internal models directly, so for any public repository with a combined commit status, any signed-in user received the owner’s password hash, hash algorithm, salt and primary email. The advisory on hash exposure through /repo/search says the reporter reproduced it on a default 28.3.0 install. Responses now carry only the status state and target URL. Hashes already fetched stay fetched, so on 28.x instances with untrusted accounts, resetting passwords for public-repository owners is a reasonable precaution.

Unlimited TOTP guesses

CVE-2026-123002 scores 8.2, but it only helps someone who already has the victim’s password. Its proof of concept is measured: 30 consecutive wrong codes all returned HTTP 200, failures went unlogged, and the reporter hit a valid code after 309,961 attempts at about 1,233 requests per second from one client, roughly four minutes of traffic. The backport in PR #40374, which limits failed TOTP attempts per account, counts five wrong or replayed codes and then refuses TOTP until 15 minutes after the last failure, covering the web 2FA page, account recovery and Basic auth with the X-Gitea-OTP header. It is narrower than a full account lock: scratch codes and WebAuthn still work while TOTP is blocked, and failures are now logged in a format the existing fail2ban filter matches.

The other 18 entries

One belongs to the toolchain. Binaries are rebuilt with Go 1.27.4 for CVE-2026-97054, an HTTP/1 server crash in net/http when a request exceeds a MaxBytesReader limit. A RubyGems compact-index forgery was already fixed in 28.3.0 and is only disclosed now, and an issue-versus-pull-request permission bug that 28.2.0 and 28.3.0 fixed in the API is finished here for issue search and milestone pages. Most of the rest are authorization gaps: users with read access could push to a repository during migration, fork or template generation, the AGit flow opened pull requests without a permission check, deactivated accounts could still get OAuth2 tokens, Git LFS served objects to anonymous clients despite REQUIRE_SIGNIN_VIEW, and a negated team ID let the built-in Actions user count toward required approvals.

What changed since 28.3

Gitea 28.3.0 came out on November 1 with 21 CVE entries of its own, so this is the second batch of that size in two weeks. The reporter credits moved: 28.3.0 credited Anthropic on two advisories, while 28.4.0 credits it on nine, all patched by silverwind. The record does not say how those bugs were found. Volume from AI-assisted work is already weighing on reviewers in other projects, as with the Linux memory-management reviewer who gave up several roles over AI-generated patches, though Gitea’s case involves reports rather than submissions. The auto-init race is also the second hook-overwrite route to command execution this year, after CVE-2026-60004 in the 1.27 line, which CISA flagged as exploited in August.

Upgrading

There is no further deadline or target date. The developers recommend that every installation move to 28.4.0 now, and the three advisories above name it as the only patched version, including for the TOTP flaw, which the reporter tested on a 1.27 build.

Christopher is a Linux and network administrator who writes about server management, security, and networking for Command Linux. Over his career he has managed web servers, mail servers, and small business networks, and his tutorials reflect problems he has solved firsthand. He is especially interested in server hardening and helping readers secure their systems from day one.