[SECURITY] ghcr.io/actions/actions-runner:2.338.2 was republished with a new digest: please make version tags immutable
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- C#
- Stars
- 6.4k
- Forks
- 1.5k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 36
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from actions/runner
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
actions/runner#4820 · 3 comments ·
Maintainers usually reply within 1 day
-
Workflow schema omits documented code-quality and copilot-requests permissionsPossibly taken @localzet claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Runner crashes at InitializeSecretMasker on machines with Thai (th-TH) culture — culture-sensitive LastIndexOf in PowerShellPreAmpersandEscapePossibly taken @CloudNinjaDev claimed this 47 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Broker retry logs an ERR stack trace and a phantom backoff on every job completion (listener's own cancellation treated as a request failure)Possibly taken @nitrobass24 claimed this 87 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
Similar issues
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 71/100
Maintainers usually reply within 1 day
-
bug debugger flaky small
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[BUG] MyAnonaMouse search turns a curly apostrophe into a space, so titles with ’ are never foundOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
About screenOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
GDMTT/JiraTaskBar#45 · 2 comments ·
Maintainers usually reply within 1 day