ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-95838

containerd: Unpack DoS via repeated opaque whiteouts

Published Oct 15, 2026 · catalog updated Oct 15, 2026 · containerd: Unpack DoS via

Check if you run it

No confirmed exploitation is on record for CVE-2026-95838. EPSS is 0.21%. Act only if a listed version of containerd: Unpack DoS via is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (containerd: Unpack DoS via).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.21%
Remediation
Version ranges on file
Affected products
go github.com/containerd/containerd · go github.com/containerd/containerd/v2 · golang github.com

### 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)

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • 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

How to fix CVE-2026-95838

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-95838. EPSS is 0.21%. Act only if a listed version of containerd: Unpack DoS via is installed.

Which versions are affected?

Compare what you have installed with < 1.7.35, <1.7.35, < 2.0.12, >= 2.2.0, < 2.2.8, >= 2.3.0, < 2.3.5. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-400: Uncontrolled Resource Consumption; CWE-407. EPSS 0.21%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Docker security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. 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

  2. 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

Sources

  • CVE.orgVulnerability recordCVE-2026-95838

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-95838

    30-day exploitation probability 0.2%

    first.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

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.