# CVE-2026-129337: Gitea push without write access to repositories still being created

> Users with only read access can push branches and tags into Gitea repositories still being created via migration, fork or template generation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/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-8cjj-9p56-j54f

## What is CVE-2026-129337?

CVE-2026-129337 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

Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforce write access. A repository that is still being created by a migration, fork or template generation has no hooks yet, so a user with read access to it could push branches and tags during that window, or after a failed migration that left the repository in that state. Git over HTTP now refuses requests to repositories that are still being created.

Weakness: CWE-862 (Missing Authorization)

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

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


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

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

## Is CVE-2026-129337 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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