# CVE-2026-86684: Gitea push mirror local path check uses the repository owner

> Repository administrators can bypass local path restrictions to modify server-side Git repositories if the owner has import permissions.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** BIT-gitea-2026-86684, GHSA-7v5j-mph8-9w6g, MINI-fprp-48cr-p3jm, MINI-p8q2-2ghx-xj5p

## What is CVE-2026-86684?

CVE-2026-86684 is a high-severity missing authorization vulnerability in Gitea Gitea, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Gitea push mirror API checked whether the repository owner, instead of the requesting user, may use local file system paths. On instances with `[security] IMPORT_LOCAL_PATHS = true`, a repository administrator who is not allowed to import local paths could add a push mirror to a local path on the server when the repository owner has that permission. Gitea then pushed the repository's refs into an existing Git repository at that path with the permissions of the Gitea process.

Weakness: CWE-863 (Incorrect Authorization)

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

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


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

Products: Gitea Gitea.

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

Upgrade gitea to 28.1.0 or later.

## Is CVE-2026-86684 being exploited?

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

## 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-86684 and fix it if it is affected.

What it is: CVE-2026-86684 is a high-severity missing authorization vulnerability in Gitea Gitea, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86684 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitea (Bitnami): affected from 1.18.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-86684/ (Markdown: https://insights.sbomify.com/CVE-2026-86684/index.md)
```

## Sources

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

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