What is 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.
The record classifies CVE-2026-123009 under weakness classes CWE-284, CWE-863. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 4 days ago.
Severity and exploitation probability
- EPSS (FIRST)
- 0.2% probability of exploitation in the next 30 days, higher than 16.7% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 0.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-11-15
Is CVE-2026-123009 being exploited?
It currently carries a trending score of 34 in the Threadlinqs vulnerability feed.
Affected products and versions
- Gitea: Gitea
How to fix CVE-2026-123009
Patch reference: https://github.com/go-gitea/gitea/pull/40131. Vendor advisory: https://github.com/go-gitea/gitea/security/advisories/GHSA-9vh6-6hgj-j5m5. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-123009
No threat campaign in the Threadlinqs corpus currently references CVE-2026-123009, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.