containerd · containerd · published 2026-10-12

CVE-2026-95838containerd: Unpack DoS via repeated opaque whiteouts

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-95838 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 13% of all CVEs. This containerd vulnerability: CVSS 4.6 (v4.0). Fixed upstream in containerd 2.3.5, 2.2.8, 2.0.12, 1.7.35. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in containerd 2.3.5, 2.2.8, 2.0.12, 1.7.35.

Patch events

  1. This monthSecurity release

    Container runtimecontainerd

    containerd security releases: 2.3.5, 2.2.8, 2.0.12, 1.7.35

    Upgrade to 2.3.52.2.82.0.121.7.35

    Why: Vendor security release for server software (most severe: CVE-2026-53495).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (13th pct)FIRST EPSS v2026.06.15
CVSS base score4.6 (v4.0)
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

containerd is an open-source container runtime. Prior to 1.7.35, 2.0.12, 2.2.8, and 2.3.5, containerd's layer unpack handler repeatedly traverses directories for certain opaque whiteout configurations. A malicious image layer can trigger repeated directory traversals while opaque whiteouts are processed. Pulling or importing the image can consume CPU, delay container startup, and reduce image-pull concurrency for unrelated deployments. This issue is fixed in versions 1.7.35, 2.0.12, 2.2.8, and 2.3.5.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →