CVE-2026-123009
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.
- Score
- –
- Published
- 2026-11-15
- Links
- NVD · cve.org · Report wrong data
Matched ports (1)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| www/gitea | gitea | 28.3.0_1 | unaddressed | ports@foss-daily.org |
Template for a VuXML entry
Check the version numbers before you commit this entry. Some ports share an entry in the CVE database with another port, such as sqlite2 and sqlite3. The version shown here may then be one that never existed for this port.
Ranges per package from the CVE rows that match this port, in pkg notation with the port's epoch and revision, every bound checked with pkg; one range per epoch the port actually had. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>gitea -- FIXME</topic>
<affects>
<package>
<name>gitea</name>
<range><ge>1.25.0</ge><lt>28.4.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>CVE-2026-123009: 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.</p>
</body>
</description>
<references>
<cvename>CVE-2026-123009</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2026-123009</url>
</references>
<dates>
<discovery>2026-11-15</discovery>
<entry>2026-11-16</entry>
</dates>
</vuln>