CVE-2026-111760 lets a malicious repository plant hooks through a submodule during a recursive clone. Fixes are backported to every release line from 2.50, and tools that bundle Git need updating too.
Gitea 28.4.0 closes a hook overwrite and a password-hash leak
EditorialBy TrustList Editorial
The fourth maintenance release of the 28 series follows the 20 advisories fixed in 28.3.0 two weeks earlier. One of its flaws has exposed repository owners’ password hashes to any signed-in user since 28.0.0.
- Version Control
- DevOps
- Application Security
- Patch Management
About Gitea 28.4.0 closes a hook overwrite and a password-hash leak
Gitea 28.4.0 closes a hook overwrite and a password-hash leak
15 November 2026: Gitea has released version 28.4.0 with fixes for more than 15 security flaws in its self-hosted Git service, among them CVE-2026-125423, which let any user allowed to create repositories run commands as the Gitea system user, and CVE-2026-123006, which handed repository owners' password hashes to any signed-in user. The project gives no severity scores and reports no attacks, and asks every instance to upgrade as soon as possible.
A push that arrives before the first commit
A repository created with the auto-init option accepted pushes before its initialisation had finished, and Gitea then built the initial commit on top of whatever was already there. A user could push a crafted tree in that window so that writing the README followed a symbolic link, overwrote a Git hook on the server and ran commands under the Gitea account. In 28.4.0 the initial commit is built in a fresh directory, and a new repository takes pushes only once it is fully initialised.
A related flaw, CVE-2026-129337, covers repositories still being created by a migration, a fork or a template: they have no server-side hooks yet, so a user with read access could push to them during that window.
Password hashes in the dashboard's search response
The repository search behind the dashboard, GET /repo/search, returned each repository's internal commit status object, and since 28.0.0 that object included the owner's full user record. Any signed-in user could read the password hash, salt and email address of the owner of any visible repository that has a commit status. The response now carries only the state and target URL.
Upgrading stops the leak but does not undo it. An instance that has run any 28.x release with open registration, or with users it does not fully trust, has reason to treat owner passwords as exposed to offline guessing and to reset them.
Second factors, workflows and protected files
Several of the other fixes matter to teams that rely on Gitea's own controls:
- CVE-2026-123002: an unlimited number of wrong TOTP passcodes was accepted at sign-in, in password reset and for Basic authentication with the X-Gitea-OTP header. Five failures now lock further attempts on the account for 15 minutes.
- CVE-2026-118535: a repository registered as an owner-level source of scoped workflows kept that role after a transfer, so its new owner's workflows ran in the previous owner's repositories with their Actions secrets and tokens.
- CVE-2026-123638: "Protected file patterns" in branch protection never matched file names that Git quotes, such as those containing a double quote or backslash, letting a user with write access change files the rule was meant to guard.
- CVE-2026-120729: a link dressed as an issue reference could run script in the session of anyone who hovered over it.
- CVE-2026-123065: a user with write access to any repository's releases could delete the stored file of any attachment on the instance if they knew its UUID.
The post also discloses CVE-2026-118389, a newline injection in the RubyGems package registry that was fixed in 28.3.0, and says the release binaries are now built with Go 1.27.4, which fixes a crash of HTTP/1 servers.
Two urgent upgrades in two weeks
Version 28.3.0 arrived on 1 November with 20 advisories of its own, including an OAuth account takeover. An instance that skipped it gets both sets of fixes by moving straight to 28.4.0, the fourth maintenance release of the 28 series. Most of the flaws need a signed-in account, so instances with open sign-up or many outside collaborators carry the most risk until they are updated.
Related on TrustList:
- Git 2.56.1 fixes six flaws, one allowing code execution on clone
- Cloudflare Artifacts, versioned Git-style storage for AI agents, starts billing on 12 November 2026
- GitHub Enterprise Cloud with data residency refuses X25519-only TLS clients from 7 October 2026
Sources
- Gitea Blog: Gitea 28.4.0 is released, 15 November 2026
- Linuxiac: Gitea 28.4 patches multiple security vulnerabilities, 16 November 2026
Categories & features
- Version Control
- DevOps
- Application Security
- Patch Management
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
Cloudflare says it will begin billing for Artifacts, its Git-compatible versioned storage for AI agents in open beta on the Workers Paid plan, on 12 November 2026, not the 15 October first announced. Pricing is per repository operation and per GB stored.
From 7 October 2026, GHE.com (GitHub Enterprise Cloud with data residency) stops accepting HTTPS clients that offer only X25519 for key agreement. Make sure P-256 is enabled in proxies, appliances and TLS libraries. SSH is not affected.
On 10 November 2026 .NET 8 and 9 left support, Python 3.10 went on 1 October and PHP 8.2 follows on 31 December. A method for finding what you run, reading each policy, and acting with months to spare.
Versions 8.0.34 and 9.0.23 are the last patches either will get. .NET 10 is the long-term release to move to, and both it and the new .NET 11 are supported until 14 November 2028.
One lets a user who can view users or audit events become an administrator, and turns critical where guest access is on. Patches shipped in September; Octopus Cloud is already fixed.
Seven are rated high, including an account takeover through OAuth2 auto-linking and fork workflows that receive repository secrets. Every release up to 28.2.0 is affected; there is no backport line.
Every musl release from 0.5.0 to 1.2.6 is affected. The maintainers ship a patch now and say 1.2.7 will follow; only programs that compile regular expressions from untrusted input are exposed.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More Version ControlThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.