# CVE-2026-94205: Gitea fork workflow approval bypass through maintainer-triggered events

> Attackers can bypass approval checks to execute arbitrary code on base repository runners by triggering maintainer events on fork pull requests.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-94205, GHSA-xh39-mxw9-34pp, MINI-cv4x-r822-gr6w, MINI-hmf8-gw77-66xp

## What is CVE-2026-94205?

CVE-2026-94205 is a critical missing authorization vulnerability in Gitea Gitea, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval.

Weakness: CWE-863 (Incorrect Authorization), CWE-441 (Unintended Proxy or Intermediary)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitea` | Bitnami | All versions | 28.0.0 |

Products: Gitea Gitea.

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

Upgrade gitea to 28.0.0 or later.

## Is CVE-2026-94205 being exploited?

There is no known exploitation of CVE-2026-94205 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-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)
- [CVE-2021-45331](https://insights.sbomify.com/CVE-2021-45331/): Reuse of one time passwords allowed in Gitea (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94205 is a critical missing authorization vulnerability in Gitea Gitea, published on 6 Oct 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-94205 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitea (Bitnami): affected all versions; fixed in 28.0.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-94205/ (Markdown: https://insights.sbomify.com/CVE-2026-94205/index.md)
```

## Sources

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

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