Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Unrated

Container Hardening Bypass in Gitea act_runner Docker Backend

IdentifiersCVE-2026-58053CWE-693

CVE-2026-58053 is a critical container hardening bypass affecting Gitea act_runner when using the Docker backend through act 0.262.0. The flaw arises because a workflow's container.options string is merged into the Docker job container HostConfig. When the runner is configured with privileged: false, it only forces the Docker Privileged flag to false, but does not sanitize or strip other dangerous Docker options. As a result, workflow-supplied flags such as --pid=host, --cap-add, and --security-opt are preserved and applied to the job container. An attacker with the ability to run a workflow on a Docker-backed runner can abuse these options to create a container with host namespaces and expanded capabilities, enabling escape from the containerized job environment to the underlying host as root despite privileged mode being disabled.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in full host compromise from a workflow execution context. An attacker can bypass intended runner isolation, obtain root-level access on the runner host, and potentially access or modify host resources, secrets, other workloads, and runner infrastructure. The impact includes high confidentiality, integrity, and availability consequences because the attacker can escape the job container and operate on the host with elevated privileges.

Mitigation

If you can’t patch tonight, do this now.

Until patched versions are deployed, do not run untrusted workflows on Docker-backed runners. Review and restrict which Docker container options may be specified in workflows, and explicitly disallow dangerous flags such as --pid=host, capability additions via --cap-add, and unsafe --security-opt values. Where possible, use more strongly isolated runner backends or additional host/container confinement controls to reduce the risk of container escape.

Remediation

Patch, then assume compromise.

Update Gitea act_runner and the underlying runner components to a version that addresses this issue and properly sanitizes workflow-supplied Docker job container options. Ensure runner configuration does not rely solely on privileged: false as a security boundary, and deploy a fixed version that rejects or strips unsafe HostConfig-related options originating from workflow container.options.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.