CVE-2026-123009

Gitea base repository code disclosure through the web editor in forks

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Gitea allows a user who has forked a repository to edit files via the web editor. During this process the system copies a branch from the base repository into the fork, but it does not verify that the editor has read access to the base repository. As a result, an individual who once had read access but has since lost it—such as when a repository is made private or a collaborator is removed—can continue to duplicate and read any current branches of the original repository. This flaw effectively bypasses normal access control, exposing potentially sensitive source code and violating confidentiality. The weakness involves improper access control (CWE‑284) and missing authorization checks (CWE‑863).

Affected Systems

The affected system is the Gitea platform, version unspecified but the vulnerability is fixed in the 28.4.0 release. Users running earlier Gitea versions that use the web editor for forked repositories are vulnerable.

Risk and Exploitability

The attack does not require advanced preparation beyond having a fork; the user merely initiates a file edit through the web interface. Because the vulnerability removes the necessity to authenticate against the base repository, any party with a fork can exploit it to read private code. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, but the impact is significant for confidentiality. The CVSS score is not provided; however, the combination of unrestricted code disclosure and the lack of a protection mechanism suggests a high severity. Managers should treat this as a critical risk for any organizations relying on Gitea to host or fork private code bases.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the official patch by upgrading Gitea to version 28.4.0 or a later release that removes the access‑check flaw when editing forks
  • Re‑evaluate repository visibility settings and ensure that private or removed collaborators cannot retain forks that still point to the base repository
  • Audit existing forked repositories for unauthorized editing activity and close or delete forks that are no longer needed

Generated by OpenCVE AI on November 15, 2026 at 22:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values 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.
Title Gitea base repository code disclosure through the web editor in forks
Weaknesses CWE-284
CWE-863
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 15, 2026, 9:13 PM
Reserved
Nov 15, 2026, 8:29 PM
Status
Deferred
Published
Nov 15, 2026, 10:17 PM
Modified
Nov 15, 2026, 10:17 PM