github.com/containerd/containerd/v2: containerd: Unpack DoS via repeated opaque whiteouts
What fixes it
- 2.0.12github.com/containerd/containerd/v2, goGitHub
go get github.com/containerd/containerd/v2@v2.0.12 - 1.7.35github.com/containerd/containerd, goGitHub
go get github.com/containerd/containerd@v1.7.35 - 2.2.8github.com/containerd/containerd/v2, goGitHub
go get github.com/containerd/containerd/v2@v2.2.8 - 2.3.5github.com/containerd/containerd/v2, goGitHub
go get github.com/containerd/containerd/v2@v2.3.5 - 2.0.12github.com/containerd/containerd/v2, GoOSV
go get github.com/containerd/containerd/v2@v2.0.12 - 1.7.35github.com/containerd/containerd, GoOSV
go get github.com/containerd/containerd@v1.7.35
Show all 8 fixed versions
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
Impact
A vulnerability exists in containerd's layer unpack handler where the processing of certain image layers causes superlinear time complexity. During the unpack operation, specific file configurations within the layer can trigger repeated directory traversals.
Consequently, pulling or importing a maliciously crafted image can result in increased unpack times and a moderate increase in CPU usage. This delays container startup, even if the compressed image layers are small. Additionally, in orchestrators like Kubernetes that apply concurrency limits to image pulls, these excessively long operations can reduce the available concurrency for other pulls, potentially delaying unrelated container deployments.
Patches
This bug has been fixed in containerd 2.3.5, 2.2.8, 2.0.12, and 1.7.35. Users should update to these versions to resolve the issue.
Workarounds
There are no known workarounds for this issue. Users are advised to only pull and import trusted images from known registries until the patch can be applied.
Credits
The containerd project would like to thank Jakub Ciolek of AlphaSense for responsibly disclosing 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](mailto:security@containerd.io)
To report a security issue in containerd:
- Report a new vulnerability
- Email us at [security@containerd.io](mailto:security@containerd.io)
Text from GitHub Advisory Database
Affected versions 13
- github.com/containerd/containerd/v2, go< 2.0.12GitHub
- github.com/containerd/containerd, go< 1.7.35GitHub
- github.com/containerd/containerd/v2, go>= 2.2.0, < 2.2.8GitHub
- github.com/containerd/containerd/v2, go>= 2.3.0, < 2.3.5GitHub
- containerdaffected: < 1.7.35CVE List
- containerdaffected: >= 2.0.0-beta.0, < 2.0.12CVE List
- containerdaffected: >= 2.2.0, < 2.2.8CVE List
- containerdaffected: >= 2.3.0, < 2.3.5CVE List
- github.com/containerd/containerd/v2, go< 2.0.12, >= 2.2.0, < 2.2.8, >= 2.3.0, < 2.3.5GitHub
- github.com/containerd/containerd/v2, Gofrom first release, fixed in 2.0.12OSV
- github.com/containerd/containerd, Gofrom first release, fixed in 1.7.35OSV
- github.com/containerd/containerd/v2, Gofrom 2.2.0, fixed in 2.2.8OSV
- github.com/containerd/containerd/v2, Gofrom 2.3.0, fixed in 2.3.5OSV
References 4
- github.com/containerd/containerd/commit/e6ca378dcfa610d06589a3ac96aa992de866e4f0Fixvia CVE List
- github.com/containerd/containerd/security/advisories/GHSA-rp3h-jf77-q9p4Advisoryvia CVE List
- github.com/advisories/GHSA-rp3h-jf77-q9p4Advisoryvia GitHub
- nvd.nist.gov/vuln/detail/CVE-2026-95838Referencevia GitHub