OESA-2026-4565: containerd security update
containerd is an industry-standard container runtime with an emphasis on simplicity, robustness and portability. It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc. Security Fix(es):
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.(CVE-2026-95838)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openeuler/containerdto a version that resolves this vulnerability.Fixed in 1.6.22-33.oe2403sp1 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 1.7.35 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 2.0.12 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 2.2.8 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 2.3.5
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems running containerd versions earlier than 1.7.35, 2.0.12, 2.2.8, or 2.3.5 are affected when they pull or import a malicious image containing certain opaque whiteout configurations.
What must occur for exploitation to affect operations?
A malicious image layer must be pulled or imported. Processing its opaque whiteouts can cause repeated directory traversals.
What is the expected operational impact?
The issue can consume CPU, delay container startup, and reduce image-pull concurrency for unrelated deployments. The provided severity vector indicates availability impact only.
Which containerd versions contain the fix?
The issue is fixed in containerd 1.7.35, 2.0.12, 2.2.8, and 2.3.5.