Skip to main content
VulnerabilityPublished

CVE-2026-95838: containerd security update

Affects containerdSource GCVE Database

0
Compare

Not known to be exploited · CVSS 4.6 Medium : upgrade to 1.2.0-330.oe2203sp4 when convenient.

Data as of 29 Oct 2026, 11:04 UTC

CVSS 4.0 base score
4.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.2.0-330.oe2203sp4
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade containerd to 1.2.0-330.oe2203sp4.

Affected software

ProductAffectedFixed in
openEuler 22.03-LTS-SP4containerdpkg:rpm/openEuler/containerd&distro=openEuler-22.03-LTS-SP4Other threatsAffected
  • <1.2.0-330.oe2203sp4
Fixed in
  • 1.2.0-330.oe2203sp4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and has been released in containerd versions 1.7.35, 2.0.12, 2.2.8, and 2.3.5. Users should upgrade to one of these fixed versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-95838 is a vulnerability in containerd, an industry-standard container runtime. Prior to versions 1.7.35, 2.0.12, 2.2.8, and 2.3.5, the layer unpack handler in containerd repeatedly traverses directories when processing certain opaque whiteout configurations. A malicious image layer can exploit this to cause repeated directory traversals, leading to high CPU usage, delayed container startup, and reduced image-pull concurrency for unrelated deployments. This issue has been fixed in the specified versions.

References

Community reviews

Loading reviews…