# CVE-2026-123009: Gitea base repository code disclosure through the web editor in forks

> Users who lost access to a Gitea repository can keep copying its branches into their fork and read the code; Gitea administrators should care.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-9vh6-6hgj-j5m5

## What is CVE-2026-123009?

CVE-2026-123009 is a medium-severity missing authorization vulnerability in Gitea, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-123009?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-123009?

No fix has been published for CVE-2026-123009 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123009 being exploited?

There is no known exploitation of CVE-2026-123009 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123009 and fix it if it is affected.

What it is: CVE-2026-123009 is a medium-severity missing authorization vulnerability in Gitea, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-123009 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123009/ (Markdown: https://insights.sbomify.com/CVE-2026-123009/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123009
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123009
- OSV: https://osv.dev/vulnerability/CVE-2026-123009

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123009/
Summaries are generated and may contain mistakes; the official description above is the record.
