CVE-2026-95838
containerd: Unpack DoS via repeated opaque whiteouts
Published Oct 15, 2026 · corrected/updated Oct 15, 2026 · evidence confidence high
### 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](https://github.com/containerd/project/blob/main/SECURITY.md). ### For more information If you have any questions or comments about this advisory: * Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose) * Email us at [security@containerd.io](mailto:security@containerd.io) To report a security issue in containerd: * [Report a new vulnerability](https://github.com/containerd/containerd/security/advisories/new) * Email us at [security@containerd.io](mailto:security@containerd.io)
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2026-95838 is a medium public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: github.com/containerd/containerd (< 1.7.35); github.com/containerd/containerd (<1.7.35); github.com/containerd/containerd/v2 (< 2.0.12); github.com/containerd/containerd/v2 (>= 2.2.0, < 2.2.8). Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: no CVSS/EPSS yet. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-400, CWE-407. Sources contributing to this record: cve_org, github, gitlab, gitlab. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Not listed as known exploited in CISA KEV. Not in the CISA KEV catalog.
Patch and remediation
No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 15, 2026 · GitHub Advisory Database
Detected
### 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
Oct 15, 2026 · GitHub Advisory Database
Updated
### 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
Affected
- go github.com/containerd/containerd< 1.7.35
- go github.com/containerd/containerd<1.7.35
- go github.com/containerd/containerd/v2< 2.0.12
- go github.com/containerd/containerd/v2>= 2.2.0, < 2.2.8
- go github.com/containerd/containerd/v2>= 2.3.0, < 2.3.5
- golang github.comversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2026-95838
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-rp3h-jf77-q9p4
containerd: Unpack DoS via repeated opaque whiteouts
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-95838
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. Thi
advisories.gitlab.com - GitLab Advisory DatabasePackage advisorygo/github.com/containerd/containerd/CVE-2026-95838.yml
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.\n\nConsequently, pulling or importing a maliciously crafted + image can result in increased unpack times and a moderate increase in CPU
gitlab.com