0.0
NA
CVE-2026-123009
Gitea base repository code disclosure through the web editor in forks
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.

INFO

Published Date :

Nov. 15, 2026, 10:17 p.m.

Last Modified :

Nov. 15, 2026, 10:17 p.m.

Remotely Exploit :

No

Source :

88ee5874-cf24-4952-aea0-31affedb7ff2
Affected Products

The following products are affected by CVE-2026-123009 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Gitea gitea
Solution
Ensure users have read access to the base repository before copying branches.
  • Verify user permissions on the base repository.
  • Enforce read access checks before copying branches.
  • Update the branch copying mechanism.
References to Advisories, Solutions, and Tools
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-123009 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-123009 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-123009 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 88ee5874-cf24-4952-aea0-31affedb7ff2

    Nov. 15, 2026

    Action Type Old Value New Value
    Added 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.
    Added CWE CWE-284
    Added CWE CWE-863
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/123xxx/CVE-2026-123009.json">CVE-2026-123009</a>
    Added Reference https://blog.gitea.com/release-of-28.4.0/
    Added Reference https://github.com/go-gitea/gitea/pull/40131
    Added Reference https://github.com/go-gitea/gitea/pull/40281
    Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.4.0
    Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-9vh6-6hgj-j5m5
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.