Gitea
Gitea command execution through repository auto-initialization
A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repository already contained. A user who is allowed to create repositories could push a crafted tree during that window so that writing the README followed a symbolic link and overwrote a server-side git hook, which runs commands as the Gitea system user. The initial commit is now built in a freshly initialized directory, and a new repository only becomes ready, and accepts pushes, once its initialization is complete.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 28.4.0
Fixed in 28.4.0
Mitigation
Upgrade Gitea to 28.4.0 or later.
References
- Vendor advisory github.com/go-gitea/gitea/security/advisories/…
- Patch github.com/go-gitea/gitea/pull/40376
- Patch github.com/go-gitea/gitea/pull/40383
2 more
- Release notes blog.gitea.com/release-of-28.4.0
- Release notes github.com/go-gitea/gitea/releases/tag/v28.4.0
Timeline
Days relative to CVE publicationFirst public PoC 13 h after publication; not in CISA KEV. First PoC: grigorovichvlad/CVE-2026-125423 (created 16 Nov 2026, found by us: 17 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| grigorovichvlad/CVE-2026-125423 | 16 Nov 2026 +13 h | 17 Nov 2026 | 0 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.