github.com/containerd/containerd/v2
Affected
- introduced
0, fixed2.0.12(semver)
Fixed versions
2.0.12
Fix
- Fixed version
2.0.12go get github.com/containerd/containerd/[email protected]
Advisory
Also known as: CVE-2026-95838, GO-2026-6796
containerd: Unpack DoS via repeated opaque whiteouts
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:
To report a security issue in containerd:
Medium Basis: The source's own band: MODERATE
0, fixed 2.0.12 (semver)2.0.12
2.0.12go get github.com/containerd/containerd/[email protected]0, fixed 1.7.35 (semver)1.7.35
1.7.35go get github.com/containerd/[email protected]2.2.0, fixed 2.2.8 (semver)2.2.8
2.2.8go get github.com/containerd/containerd/[email protected]2.3.0, fixed 2.3.5 (semver)2.3.5
2.3.5go get github.com/containerd/containerd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0