# CVE-2026-73802: Gitea Runner host isolation bypass through container options

> A workflow author can bypass container isolation in Gitea Runner to execute commands as root on the host system.

- **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:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** CLEANSTART-2026-DC26983, GHSA-x4q3-gcj3-m6cf, GO-2026-6656, MINI-6px9-7787-jwv6, MINI-fq68-5q79-q2j8

## What is CVE-2026-73802?

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

### Official description

Gitea Runner passes workflow-controlled container options into Docker job container configuration while privileged mode is disabled. Host namespace settings, expanded capabilities, and security profile overrides can remain effective despite Privileged being forced false. A workflow author able to run jobs on an affected Docker-backed runner can use these options to access host namespaces and execute commands as root on the runner host, bypassing the intended container isolation.

Weakness: CWE-269 (Improper Privilege Management)

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

3 open source packages ship an affected version, including gitea.com/gitea/runner.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitea.com/gitea/runner` | Go | All versions | 1.0.9-0.20260731160927-34bfa1915022 |
| `gitea.com/gitea/runner` | Go | All versions | 1.0.9-0.20260731160927-34bfa1915022 |
| `gitea.com/gitea/runner` | Go | All versions | 1.0.9-0.20260731160927-34bfa1915022 |

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

Upgrade gitea.com/gitea/runner to 1.0.9-0.20260731160927-34bfa1915022 or later.

## Is CVE-2026-73802 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- gitea.com/gitea/runner (Go): affected all versions; fixed in 1.0.9-0.20260731160927-34bfa1915022
- gitea.com/gitea/runner (Go): affected all versions; fixed in 1.0.9-0.20260731160927-34bfa1915022
- gitea.com/gitea/runner (Go): affected all versions; fixed in 1.0.9-0.20260731160927-34bfa1915022

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

## Sources

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

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