CVE-2026-123009 json
Gitea base repository code disclosure through the web editor in forks
published 2d ago modified yesterday also EUVD-2026-126122 , GHSA-9vh6-6hgj-j5m5
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository go-gitea/gitea. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go gitea.dev 28.4.0
- Gitea Gitea 28.4.0
- github.com/go-gitea/gitea#40131 pull request
- github.com/go-gitea/gitea#40281 pull request
- github.com/go-gitea/gitea/releases/tag/v28.4.0 release
Is CVE-2026-123009 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | gitea.dev | >=1.25, <=28.3.0 |
28.4.0 |
Affected products
- Gitea Gitea
Classification
- Weakness
- Technology feeds
References
-
github.com
/go-gitea/gitea/pull/40131
patch
-
github.com
/go-gitea/gitea/pull/40281
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-9vh6-6hgj-j5m5
vendor-advisory, advisory
-
blog.gitea.com
/release-of-28.4.0/
release-notes
-
github.com
/go-gitea/gitea/releases/tag/v28.4.0
release-notes
Sources
- CVE List CVE-2026-123009
- NVD CVE-2026-123009
- Maintainer advisory GHSA-9vh6-6hgj-j5m5
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of go-gitea/gitea published their own advisory on GitHub. Reviewed sources take precedence over it.