CVE-2026-95838: 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.
Published Oct 15, 2026
Affected packages
github.com/containerd/containerd/v2
- Ecosystem
- Go
- Affected
- < 2.0.12
- Fixed in
- 2.0.12
- Check
go list -m github.com/containerd/containerd/v2
github.com/containerd/containerd
- Ecosystem
- Go
- Affected
- < 1.7.35
- Fixed in
- 1.7.35
- Check
go list -m github.com/containerd/containerd
github.com/containerd/containerd/v2
- Ecosystem
- Go
- Affected
- >= 2.2.0, < 2.2.8
- Fixed in
- 2.2.8
- Check
go list -m github.com/containerd/containerd/v2
github.com/containerd/containerd/v2
- Ecosystem
- Go
- Affected
- >= 2.3.0, < 2.3.5
- Fixed in
- 2.3.5
- Check
go list -m github.com/containerd/containerd/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 [[email protected]](mailto:[email protected])
To report a security issue in containerd:
- Report a new vulnerability
- Email us at [[email protected]](mailto:[email protected])
Credited to jake-ciolek.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-95839
containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor
high7.1Nov 19, 2026CVE-2026-95837
containerd CRI plugin: Checkpoint restore bypasses destination security context
high7.8Oct 15, 2026CVE-2026-53493
Containerd has image-pull DoS via crafted OCI index graph amplification
medium6.9Sep 25, 2026CVE-2026-53495
containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service
medium6.8Sep 9, 2026CVE-2026-47262
containerd image-triggered runtime DoS via unbounded group parsing
medium6.9Jun 19, 2026CVE-2026-50195
containerd: CRI checkpoint import allows local image tag poisoning
medium9.9Jun 19, 2026
