Gitea Runner
Gitea Runner host isolation bypass through container options
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.0.0
Fixed in 3.0.0
Mitigation
Upgrade Gitea Runner to 3.0.0 or later.
References
- Vendor advisory github.com/go-gitea/gitea/security/advisories/…
- Release notes blog.gitea.com/release-of-runner-3.0.0
- Release notes gitea.com/gitea/runner/releases/tag/v3.0.0
Timeline
Days relative to CVE publicationFirst public PoC 26 days after publication; not in CISA KEV. First PoC: sn0x-sharma/Gitea2shell-Sandbox-Escape-to-Host-RCE (created 9 Nov 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| sn0x-sharma/Gitea2shell-Sandbox-Escape-to-Host-RCE | 9 Nov 2026 +26 d | 14 Nov 2026 | 1 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.