OESA-2026-4565: containerd security update

Published Oct 29, 2026
·
Updated

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

1 affected componentFixes available
openeuler/containerd<1.6.22-33.oe2403sp1
1.6.22-33.oe2403sp1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade openeuler/containerd to a version that resolves this vulnerability.

    Fixed in 1.6.22-33.oe2403sp1
  2. Upgrade

    Upgrade containerd to a version that resolves this vulnerability.

    Fixed in 1.7.35
  3. Upgrade

    Upgrade containerd to a version that resolves this vulnerability.

    Fixed in 2.0.12
  4. Upgrade

    Upgrade containerd to a version that resolves this vulnerability.

    Fixed in 2.2.8
  5. Upgrade

    Upgrade containerd to a version that resolves this vulnerability.

    Fixed in 2.3.5

Event History

Oct 29, 2026
Advisory Published
via OSV·09:03 AM
Data Sourced
via OSV·09:03 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203