actions / actions/actions-runner-controller

Git version used in summerwind/actions-runner-dind image is outdated and vulnerable

Open
#4,244 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug community needs triage
Dominant language
Go
Stars
6.5k
Forks
1.5k
Avg merge
2d 2h
Merged PRs (30d)
27

Description

Checks
Controller Version

v0.27.0

Helm Chart Version

0.22.0

CertManager Version

No response

Deployment Method

ArgoCD

cert-manager installation

No we are not using cert-manager installation

Checks
  • This isn't a question or user support case (For Q&A and community support, go to Discussions. It might also be a good idea to contract with any of contributors and maintainers if your business is so critical and therefore you need priority support
  • I've read releasenotes before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
  • My actions-runner-controller version (v0.x.y) does support the feature
  • I've already upgraded ARC (including the CRDs, see charts/actions-runner-controller/docs/UPGRADING.md for details) to the latest and it didn't fix the issue
  • I've migrated to the workflow job webhook event (if you using webhook driven scaling)
Resource Definitions
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: example
spec:
  replicas: 1
  template:
    metadata:
      annotations:
  spec:
      dockerdContainerResources: {}
      dockerdWithinRunnerContainer: true
      githubAPICredentialsFrom:
  
---
apiVersion: actions.summerwind.dev/v1alpha1
kind: HorizontalRunnerAutoscaler
metadata:
  name:
spec:
  maxReplicas: 2
  metrics:
    - scaleDownAdjustment: 1
      scaleDownThreshold: '0.3'
      scaleUpAdjustment: 1
      scaleUpThreshold: '0.75'
      type: PercentageRunnersBusy
  minReplicas: 1
To Reproduce
Option 1 – Using kubectl exec
Deploy the runner-controller with image summerwind/actions-runner-dind:v2.328.0-ubuntu-20.04.
Identify the runner pod:
kubectl get pods -n <namespace>
Access the pod:
kubectl exec -it <runner-pod-name> -n <namespace> -- /bin/bash
Run:
git --version
Expected output:
git version 2.38.0

Option 2 – Add a Step in Workflow
Add the following step to your GitHub Actions workflow:
- name: Check Git version
  run: git --version

Run the workflow and check the logs for:
git version 2.38.0
Describe the bug

The GitHub Actions Runner Controller uses a base image that includes an outdated version of Git.

Currently, I am using runner version v2.328.0-ubuntu-20.04, which includes Git 2.38.0. This version is affected by a known security vulnerability.

Security Advisory Reference

Git Security Advisory – GHSA-vwqx-4fm8-6qc9

Impact

Using an outdated Git version may expose the environment to known security vulnerabilities.

Recommended action: Upgrade Git to the latest version (e.g., 2.51.0 or newer) or at least a patched version.

Describe the expected behavior

The runner-controller image should include a secure and up-to-date version of Git (e.g., version 2.51.0 or newer) that is not affected by known security vulnerabilities.

When running git --version inside the runner pod, it should return a safe, patched version such as:

git version 2.51.0

Whole Controller Logs
not necessary
Whole Runner Pod Logs
√ Connected to GitHub

Current runner version: '2.328.0'
2025-09-10 06:04:29Z: Listening for Jobs
Additional Context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named in the issue. Start by locating the Dockerfile or image-build entry point for summerwind/actions-runner-dind and its Git package definition; verify the resulting runner image with git --version, and consider the work done when it reports a patched version such as 2.51.0 or newer.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, git, ubuntu
Domain
devops, infrastructure, security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.