# CVE-2026-120725: Gitea anonymous Git LFS access despite required sign-in

> Anonymous clients can download objects from private repositories via Gitea Git LFS endpoints despite sign-in being required.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-8pmc-9g44-v9gw

## What is CVE-2026-120725?

CVE-2026-120725 is a low-severity missing authorization vulnerability in Gitea, published on 15 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

With `REQUIRE_SIGNIN_VIEW = true`, the Git LFS endpoints still answered unauthenticated requests for repositories that are not private. An anonymous client who knows the path of such a repository and the SHA-256 of an LFS object could download the object, and could use the batch endpoint to test whether an object exists. The Git LFS endpoints now require authentication when sign-in is required to view the instance.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

Only installations with a non-default setting turned on are exposed.


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

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

## Is CVE-2026-120725 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120725 is a low-severity missing authorization vulnerability in Gitea, published on 15 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-120725 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

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-120725/ (Markdown: https://insights.sbomify.com/CVE-2026-120725/index.md)
```

## Sources

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

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