CVE-2026-129337 Gitea push without write access to repositories still being created
Users with only read access can push branches and tags into Gitea repositories still being created via migration, fork or template generation.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- None listed
What is CVE-2026-129337?
CVE-2026-129337 is a medium-severity missing authorization vulnerability in Gitea, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforce write access. A repository that is still being created by a migration, fork or template generation has no hooks yet, so a user with read access to it could push branches and tags during that window, or after a failed migration that left the repository in that state. Git over HTTP now refuses requests to repositories that are still being created.
Weakness: CWE-862
Which versions are affected by CVE-2026-129337?
An affected version is exposed as installed. No special setting or call is needed.
How do I fix CVE-2026-129337?
No fix has been published for CVE-2026-129337 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-129337 being exploited?
There is no known exploitation of CVE-2026-129337 in the wild and no public exploit code.
Sources
Also known as GHSA-8cjj-9p56-j54f.