Skip to content

← Actionable
Critical, CVSS 9.9amended

gitea-runner: workflow container.options passes host namespaces and capability flags to job container when privileged mode is disabled

CVE-2026-73802GHSA-x4q3-gcj3-m6cf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (gitea.com/gitea/runner 1.0.9-0.20260731160927-34bfa1915022), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Go gitea.com/gitea/runner

    Affected
    < 1.0.9-0.20260731160927-34bfa1915022
    Fixed in
    1.0.9-0.20260731160927-34bfa1915022

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-73802: 0.55% estimated exploitation activity in the next 30 days; percentile 45.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary actrunner appends workflow-controlled jobs.<job.container.options directly to the Docker HostConfig for the job container. When runner privileged mode is disabled, only Privileged is forced false. Host namespace flags, capability expansion, and security profile overrides from workflow YAML are preserved in the final HostConfig. A workflow author can enter host PID/IPC namespaces and execute commands on the runner host as root. Details Source-to-sink path in actrunner: - ContainerSpec.Options accepts workflow YAML container.options - RunContext.options() appends workflow options to runner-level container options - Job container is created with Privileged: rc.Config.Privileged but also with Options: rc.options(ctx) - mergeContainerConfigs() parses Docker CLI-style options into HostConfig - When privileged mode is disabled, only copts.privileged is forced false - sanitizeConfig() only filters Binds and Mounts - Preserved dangerous HostConfig fields: Attacker workflow YAML:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-x4q3-gcj3-m6cf

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6656

  3. Revision 1 · created ·

    Published from osv record GHSA-x4q3-gcj3-m6cf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73802

Advisory: gitea-runner: workflow container.options passes host namespaces and capability flags to job container when privileged mode is disabled
IDs: CVE-2026-73802, GHSA-x4q3-gcj3-m6cf
Record: https://patchnext.com/advisories/cve-2026-73802 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gitea.com/gitea/runner 1.0.9-0.20260731160927-34bfa1915022. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go gitea.com/gitea/runner: affected < 1.0.9-0.20260731160927-34bfa1915022; fixed in 1.0.9-0.20260731160927-34bfa1915022

## Suggested inspection (read-only)
- Go gitea.com/gitea/runner: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gitea.com/gitea/runner.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6656 (OSV record GO-2026-6656 lists affected ranges: Go gitea.com/gitea/runner >=0 <1.0.9-0.20260731160927-34bfa1915022 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-x4q3-gcj3-m6cf (OSV record GHSA-x4q3-gcj3-m6cf lists affected ranges: Go gitea.com/gitea/runner >=0 <1.0.9-0.20260731160927-34bfa1915022 (fixed))
- Verified: https://github.com/advisories/GHSA-x4q3-gcj3-m6cf (GitHub-reviewed advisory GHSA-x4q3-gcj3-m6cf lists affected ranges: Go gitea.com/gitea/runner >=0 <1.0.9-0.20260731160927-34bfa1915022)

Commands are suggestions: review each one before running it.

Loading voting…