# CVE-2026-71184: Gitea fork workflow approval bypass through review events

> Attackers can bypass fork workflow approval gates in Gitea to execute arbitrary code on base repository runners via review events.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-7w2r-xwp6-mh6c

## What is CVE-2026-71184?

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

### Official description

Gitea's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the run as originating from a fork. Review comment and review approval or rejection events can consequently load workflow code from the fork head and run it on the base repository's runners without the required maintainer approval. This allows execution of fork-controlled workflow code across the intended approval boundary.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-71184 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71184 is a high-severity vulnerability in Gitea, published on 14 Oct 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-71184 in the wild and no public exploit code.

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

## Sources

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

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