Gitea Runner host isolation bypass through container options
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Runner 3.0.0.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Gitea | Runner | <3.0.0 | 3.0.0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Gitea, strongest first
Embed
A live severity badge for an advisory, README or ticket