CVE-2026-123009

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.

Severity
MEDIUM
CVSS v3
4.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N · source adp
Exploit chance (EPSS)
0.273%
chance of exploitation in the next 30 days
higher than 19.9% of scored CVEs · 2026-11-18
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationnone
Automatableno
Technical impactpartial
Scored2026-11-16

Timeline

  1. 2026-11-15Published by the CNA21:13 UTC
  2. 2026-11-15Published in NVD22:17 UTC · 1 hour 3 minutes after the CNA
  3. 2026-11-16CISA SSVC decision recorded1 day after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
gitea giteafrom 1.25.0 before 28.4.0fixed in 28.4.028.4.0

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources