CVE-2026-123009 Gitea base repository code disclosure through the web editor in forks
Users who lost access to a Gitea repository can keep copying its branches into their fork and read the code; Gitea administrators should care.
- 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-123009?
CVE-2026-123009 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
When a file is edited in a fork through the web editor, Gitea can first copy a branch from the base repository into the fork. That copy did not check whether the user may read the base repository's code. A user who had forked a repository and later lost access to it, for example after it was made private or they were removed as a collaborator, could keep copying its current branches into their fork and read them. The copy now requires read access to the code of the base repository.
Which versions are affected by CVE-2026-123009?
An affected version is exposed as installed. No special setting or call is needed.
How do I fix CVE-2026-123009?
No fix has been published for CVE-2026-123009 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-123009 being exploited?
There is no known exploitation of CVE-2026-123009 in the wild and no public exploit code.
Sources
Also known as GHSA-9vh6-6hgj-j5m5.