[SECURITY] ghcr.io/actions/actions-runner:2.338.2 was republished with a new digest: please make version tags immutable
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 18/100
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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) fromactions/runner. - The rebuild checked out
releases/m338atd1eb12d4, the commit of tagv2.338.2. - The release asset
actions-runner-linux-x64-2.338.2.tar.gzwas 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:
- 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.
- A version tag that changes is not reproducible.
2.338.2pulled in October and2.338.2pulled now are different images. - There was no announcement: no release note, no changelog entry, no new tag. The only trace is a manual workflow run.
- 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
- Resolve the tag:
crane digest ghcr.io/actions/actions-runner:2.338.2(or a registry HEAD request for the manifest). - Compare with the digest that
release.ymlrun 40339492476 pushed on 2026-10-26. - See that the digests are different, and that
docker-publish.ymlrun 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.2immutable, and publish rebuilds as2.338.2-<date>or2.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.
- 主要言語
- C#
- スター
- 6.4k
- フォーク
- 1.5k
- 平均マージ
- 1日 7時間
- マージ済み PR(30日)
- 36
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
actions/runner のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
actions/runner#4820 · コメント 3 件 ·
メンテナーはふだん 1 日以内に返信
-
Workflow schema omits documented code-quality and copilot-requests permissions対応中かも @localzet が 12 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
actions/runner#4692 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Runner crashes at InitializeSecretMasker on machines with Thai (th-TH) culture — culture-sensitive LastIndexOf in PowerShellPreAmpersandEscape対応中かも @CloudNinjaDev が 47 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
メンテナーはふだん 1 日以内に返信
-
Broker retry logs an ERR stack trace and a phantom backoff on every job completion (listener's own cancellation treated as a request failure)対応中かも @nitrobass24 が 87 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
似ている issue
-
bug module
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1〜3時間 初心者へのやさしさ 78/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 79/100
Tichau/FileConverter#829 ·
メンテナーはふだん 9 日以内に返信
-
needs triage
難易度 1/5 1時間未満 初心者へのやさしさ 71/100
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
majorsilence/Majorsilence.Forms#718 ·
メンテナーはふだん 1 日以内に返信