# CVE-2026-89182: Gitea push-to-create bypass of FORCE_PRIVATE policy

> Attackers can bypass the FORCE_PRIVATE policy to make new repositories public when this specific configuration is enabled.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** BIT-gitea-2026-89182, GHSA-fx95-gwfc-grgc, MINI-m49g-5gp8-whmv, MINI-q7w6-pfm4-w84f

## What is CVE-2026-89182?

CVE-2026-89182 is a medium-severity vulnerability in Gitea Gitea, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instance policy. The default configuration is not affected.

Weakness: CWE-863 (Incorrect Authorization)

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

1 open source package ship an affected version, including gitea. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitea` | Bitnami | From 1.27.0 | 28.1.0 |

Products: Gitea Gitea.

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

Upgrade gitea to 28.1.0 or later.

## Is CVE-2026-89182 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89182 exists.

## Other vulnerabilities in Gitea Gitea

- [CVE-2026-60004](https://insights.sbomify.com/CVE-2026-60004/): Gitea Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-73278](https://insights.sbomify.com/CVE-2026-73278/): Gitea WebAuthn bypass during OAuth and OIDC sign-in (critical 9.8)
- [CVE-2026-94205](https://insights.sbomify.com/CVE-2026-94205/): Gitea fork workflow approval bypass through maintainer-triggered events (critical 9.8)
- [CVE-2022-42968](https://insights.sbomify.com/CVE-2022-42968/): Gitea vulnerable to Argument Injection (critical 9.8)
- [CVE-2021-45330](https://insights.sbomify.com/CVE-2021-45330/): Improper Privilege Management in Gitea (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89182 is a medium-severity vulnerability in Gitea Gitea, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89182 exists.

Affected packages and fixed versions:
- gitea (Bitnami): affected from 1.27.0; fixed in 28.1.0

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

## Sources

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

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