CVE-2026-95839: containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor
High
- OSV id
- GHSA-vwhp-8p66-mq4f
- Also known as
- CVE-2026-95839
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
>= 2.2.0, < 2.2.10 | 2.2.10 |
| github.com/containerd/containerd/v2 Go |
>= 2.3.0, < 2.3.7 | 2.3.7 |
| github.com/containerd/containerd/v2 Go |
>= 2.4.0, < 2.4.2 | 2.4.2 |
How to fix it
github.com/containerd/containerd/v2 (Go)
Upgrade github.com/containerd/containerd/v2 to 2.2.10 or later.
go get github.com/containerd/containerd/v2@v2.2.10
go mod tidy
- Indirect Go modules are upgraded the same way (`go get module@version`).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
github.com/containerd/containerd/v2 (Go)
Upgrade github.com/containerd/containerd/v2 to 2.3.7 or later.
go get github.com/containerd/containerd/v2@v2.3.7
go mod tidy
- Indirect Go modules are upgraded the same way (`go get module@version`).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
github.com/containerd/containerd/v2 (Go)
Upgrade github.com/containerd/containerd/v2 to 2.4.2 or later.
go get github.com/containerd/containerd/v2@v2.4.2
go mod tidy
- Indirect Go modules are upgraded the same way (`go get module@version`).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
Impact
A bug in containerd's image manifest processing causes an unrecovered panic when a child descriptor contains the io.containerd.manifest.subject annotation and a malformed digest. Pulling or importing such an image through the transfer service (including default CRI PullImage requests) crashes the containerd daemon. In Kubernetes environments, kubelet retries failed image pulls with backoff, allowing a pod referencing an untrusted image to repeatedly crash containerd and disrupt container operations on the worker node.
Patches
This bug has been fixed in containerd 2.4.2, 2.3.7, and 2.2.10. Users should update to these versions to resolve the issue.
Workarounds
Restrict pod image references to trusted registries (for example, using a Kubernetes ValidatingAdmissionPolicy or admission webhook) and only pull or import images from trusted sources.
Credits
The containerd project would like to thank @melihgurlek, LEI WANG (@ssst0n3) and Haoyuan Zhang (@zj1ng7), and OpenSec Intelligence who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
- Open an issue in containerd
- Email us at security@containerd.io
To report a security issue in containerd:
- Report a new vulnerability
- Email us at security@containerd.io
References
- GHSA-vwhp-8p66-mq4f on OSV.dev
- Web: https://github.com/containerd/containerd/security/advisories/GHSA-vwhp-8p66-mq4f
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-95839
- Web: https://github.com/containerd/containerd/commit/20a3b31390653d7a83fdaeb0c318b01a263c9d9a
- Web: https://github.com/containerd/containerd/commit/2181d7baa2a303ea2082e5c0f1a7697787b61ef2
- Web: https://github.com/containerd/containerd/commit/2455fec2f7bfa63adb1f993c63ba0cea9cdedb8c
- Web: https://github.com/containerd/containerd/commit/a2eb01f667b320b00ec218216f26f7b79197d4cd
- Package: https://github.com/containerd/containerd
- Web: https://github.com/containerd/containerd/releases/tag/v2.2.10
- Web: https://github.com/containerd/containerd/releases/tag/v2.3.7
- Web: https://github.com/containerd/containerd/releases/tag/v2.4.2
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.