GITEA.DEV · CVE-2026-123006 · Package
FIX → 28.4.0
The /repo/search endpoint in Gitea serializes the internal commit status object, which includes the owner's full user record. Any signed-in user can read password hashes, salts, and primary emails of owners of public repositories that have a commit status, enabling offline password cracking and account enumeration.
first public Nov 15, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Self-hosted Gitea instances running versions 28.0.0 through 28.3.0 with users able to sign in, since any authenticated user can query the search endpoint. Repositories that have no commit status are not exposed through this path. Instances on managed hosting that patched or run a fixed version can skip it.
Not affected if managed-hosting, no-public-repos-with-commit-status, version-28.4.0-or-later
Who cares gitea, go, self-hosted
gitea --version; versions from 28.0.0 through 28.3.0 are affected.go-gitea/gitea source and not a managed host (check with the admin)./repo/search as a signed-in user on a test instance and look for Passwd or Salt in the JSON.Any authenticated user (no privileges needed) can read the password hash, hash algorithm, salt, rands and primary email of the owner of any public repository that has a latest combined commit status. /repo/search serializes the internal CommitStatus → Repository → user_model.User object graph directly, without a DTO or json exclusion.
Root cause: the web repo search response embeds the internal commit-status model and JSON-encodes the full object graph.
json:"-", and commitstatus_service sets it to the full repo (services/repository/commitstatus/commitstatus.go:196).Result: the response contains latest_commit_status.Repo.Owner.{Passwd,PasswdHashAlgo,Salt,Rands,Email} plus the whole internal Repository object.
Fix: build a minimal DTO for search results, or add json:"-" to CommitStatus.Repo/Owner and add a test asserting the search JSON never contains Passwd/Salt/Rands/Email.
Tested on a fresh Gitea v28.3.0 (commit 4f5a3e1), default settings.
Any signed-in user can harvest Argon2id password hashes, salts, hash parameters and primary emails for every owner of a public repository with a commit status — offline cracking material and account enumeration. The same response also leaks the full internal repository object.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
Upgrade to 28.4.0
28.4.0 or later.NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.