dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-58053

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Gitea act_runner (through act 0.2620.0) with the Docker backend fails to properly sanitize container options when privileged mode is disabled. While the runner correctly prevents the Privileged flag from being set, it passes through dangerous options like --pid=host, --cap-add, and --security-opt unchanged from the workflow's container.options string. This allows attackers who can trigger workflows to escape container isolation and gain root access on the host by leveraging host namespaces and elevated capabilities despite privileged mode being explicitly disabled.

MitigationRestrict workflow execution permissions on Docker-backed runners to trusted users only, and validate/sanitize all container.options parameters before passing them to Docker. Consider using alternative job runners (e.g., native Gitea Actions, hostname-based runners) for untrusted workflows until a patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Gitea act_runner with Docker backend is in use
    Review your Gitea instance configuration files (typically in /etc/gitea/, ~/.gitea/, or the Docker compose setup) for act_runner registration and verify the runner uses the Docker executor. Look for files like .env, config.yaml, or docker-compose.yml containing 'act_runner' and 'executor: docker' or similar Docker backend settings.
    Affected if act_runner is deployed and configured to use Docker as the executor backend for running workflows
  2. Locate workflow files that specify container.options
    Search repository workflow directories (typically .github/workflows/, .gitea/workflows/, or .workflow/) for YAML files containing a 'container:' or 'jobs.<job>.container:' key with an 'options:' or 'options_string:' parameter. Run: find /path/to/repos -path '*/.gitea/workflows/*.yml' -o -path '*/.github/workflows/*.yml' 2>/dev/null | xargs grep -l 'options'
    Affected if Workflow files contain container options parameters that could pass through Docker flags
  3. Inspect container.options for dangerous flags
    Examine all workflow files identified in the previous step. Look specifically for the following patterns within container.options strings: '--pid=host', '--pid host', '--cap-add', '--cap-add=', '--security-opt', '--security-opt='. These can be embedded within a larger options string.
    Affected if Any workflow file contains --pid=host, --cap-add, or --security-opt in the container options parameter
  4. Check runner configuration for disabled privileged mode
    Review the act_runner configuration (config.yaml or environment variables) for the Docker executor settings. Look for 'privileged: false' or similar settings that indicate privileged mode was intentionally disabled. This confirms the runner attempts to block privileged mode but may still pass through other dangerous options.
    Affected if The runner configuration shows privileged mode is explicitly disabled, which would be the intended safe configuration but is insufficient due to this vulnerability

A user is affected if they run Gitea act_runner with the Docker backend, allow workflow files to define container.options, and any workflow contains --pid=host, --cap-add, or --security-opt in those options regardless of privileged mode being disabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict workflow execution permissions on Docker-backed runners to trusted users only, and validate/sanitize all container.options parameters before passing them to Docker. Consider using alternative job runners (e.g., native Gitea Actions, hostname-based runners) for untrusted workflows until a patch is available.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58053 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data