[SECURITY] ghcr.io/actions/actions-runner:2.338.2 was republished with a new digest: please make version tags immutable

Aperta
#4,860 0 commenti 3 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
18/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, github-actions
Ambito
ci-cd, security

Direzione di ricerca

Start with the two publishing workflows the issue names, release.yml (run 40339492476) and docker-publish.yml (run 43082958818), and compare how each one tags and pushes the ghcr.io/actions/actions-runner image. The reported digests are in the issue table. Done means a decided tag policy that keeps released version tags from moving, plus a note in the release docs. Changing the workflows needs maintainer sign-off on the policy first.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Describe the bug

The image tag ghcr.io/actions/actions-runner:2.338.2 changed its digest after the release. A released version tag now points to a different image, without a new tag or an announcement.

Index digest Built from Base image (dotnet/runtime-deps:8.0-noble)
2026-10-26 (release) sha256:759a1d94a15b05941aba5196974ff43fe15b4cbba29b694b35cbc32a1166b232 release.yml, run 40339492476 sha256:92c9ed3c3f2911031fd5b4f4093ac0cab69c99d9ee1adc66b82a2c4d52378db8
2026-11-11 (now) sha256:6d0b2d80d80f143f77dcb676e50920100bbb547e39e883454d57f45ab8c31300 docker-publish.yml (workflow_dispatch), run 43082958818 sha256:7745316518f2abec3e133889558c2e8d4b616d3ca138db4c5b8c0914a0af3919

We understand that this is a rebuild of the same runner version on a newer base image. We checked the following:

  • Both digests have a valid build provenance attestation (gh attestation verify --owner actions) from actions/runner.
  • The rebuild checked out releases/m338 at d1eb12d4, the commit of tag v2.338.2.
  • The release asset actions-runner-linux-x64-2.338.2.tar.gz was not changed after 2026-10-26.
  • The new base digest is the current mcr.microsoft.com/dotnet/runtime-deps:8.0-noble.

Even if this is not a compromised image, the tag policy is a serious supply-chain security concern:

  1. For a consumer, "same version tag, new digest" looks the same as a registry or account compromise. To tell them apart, we had to read workflow runs, logs, attestations and release assets.
  2. A version tag that changes is not reproducible. 2.338.2 pulled in October and 2.338.2 pulled now are different images.
  3. There was no announcement: no release note, no changelog entry, no new tag. The only trace is a manual workflow run.
  4. Consumers who pin by digest (as recommended for supply-chain security) see their checks fail, and they cannot find out from the project why.

To Reproduce

  1. Resolve the tag: crane digest ghcr.io/actions/actions-runner:2.338.2 (or a registry HEAD request for the manifest).
  2. Compare with the digest that release.yml run 40339492476 pushed on 2026-10-26.
  3. See that the digests are different, and that docker-publish.yml run 43082958818 pushed the new one on 2026-11-11.

Expected behavior

A released version tag points to one image for its whole life. Rebuilds on a new base image use a new tag. For example:

  • keep 2.338.2 immutable, and publish rebuilds as 2.338.2-<date> or 2.338.2-r2, or
  • if the plain version tag must move, also publish an immutable tag per build, and document that the plain tag can move.

In both cases, please announce rebuilds (for example in the release notes or a pinned discussion), with the old digest, the new digest and the reason (for example, "base image refresh for CVE fixes").

It would also help to document the tag policy of ghcr.io/actions/actions-runner (related: #4456).

Runner Version and Platform

Runner 2.338.2, image ghcr.io/actions/actions-runner, linux/amd64. We use it as the base of our self-hosted runner image and pin it by digest.

What's not working?

Our image build checks that the pinned base digest is still the digest of the version tag. Since 2026-11-11 this check fails:

FROM version    : 2.338.2
Pinned digest   : sha256:759a1d94a15b05941aba5196974ff43fe15b4cbba29b694b35cbc32a1166b232
Upstream digest : sha256:6d0b2d80d80f143f77dcb676e50920100bbb547e39e883454d57f45ab8c31300

Job Log Output

Not applicable.

Runner and Worker's Diagnostic Logs

Not applicable.

Lingua principale
C#
Stelle
6.4k
Fork
1.5k
Merge medio
1g 7h
PR unite (30g)
36

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di actions/runner

Tutte le issue di actions/runner

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.