# CVE-2026-58053: Gitea act_runner - Container Hardening Bypass via Workflow Container Options

> Attackers can escape Docker containers to gain root access on the host by injecting unsafe container options in Gitea act_runner workflows.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA: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:** 28 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-8qf9-pc52-j7cm

## What is CVE-2026-58053?

CVE-2026-58053 is a critical vulnerability in Gitea act_runner, published on 28 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gitea act_runner with the Docker backend (through act 0.262.0) passes a workflow's container.options string to the Docker job container's HostConfig and, when configured with privileged: false, forces only the Privileged flag off while merging options such as --pid=host, --cap-add, and --security-opt unchanged. A user who can run a workflow on a Docker-backed runner can create a job container with host namespaces and broad capabilities and escape to the host as root despite privileged mode being disabled.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-58053 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58053 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58053 is a critical vulnerability in Gitea act_runner, published on 28 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58053 exists.

Affected product: Gitea act_runner. 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-58053/ (Markdown: https://insights.sbomify.com/CVE-2026-58053/index.md)
```

## Sources

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

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