Ce mail provient de l'extérieur, restons vigilants ===================================================================== CERT-Renater Note d'Information No. 2026/VULN879 _____________________________________________________________________ DATE : 10/09/2026 HARDWARE PLATFORM(S): / OPERATING SYSTEM(S): Systems running containerd/v2 (Go) versions prior to 2.3.5, 2.2.8, 2.0.12, containerd (Go) versions prior to 1.7.35. ===================================================================== https://github.com/containerd/containerd/security/advisories/GHSA-p7v4-vr35-mj6f https://github.com/containerd/containerd/security/advisories/GHSA-7jxh-36q5-gcqv https://github.com/containerd/containerd/security/advisories/GHSA-rp3h-jf77-q9p4 _____________________________________________________________________ containerd CRI plugin: Checkpoint restore bypasses destination security context Critical samuelkarp published GHSA-p7v4-vr35-mj6f Package github.com/containerd/containerd/v2 (Go) Affected versions >= 2.1.0 < 2.2.7, >= 2.3.0 < 2.3.4 Patched versions >= 2.2.7, >= 2.3.4 Description Impact A vulnerability in containerd's CRI implementation allows a container restored from an untrusted checkpoint via the CreateContainer API to bypass the destination security context and execute with elevated privileges. When restoring a container from a checkpoint archive or annotated OCI image, CRIU restores process credentials, Linux capabilities, no_new_privs, and seccomp state directly from checkpoint data rather than enforcing the destination CRI ContainerConfig. An attacker who can run a container with a crafted checkpoint image can execute processes as root with full capabilities and no enforced seccomp filters despite restrictive security policies requested by the orchestrator. Additionally, containerd's CRI status reporting reflects the requested configuration rather than the actual restored process state, masking the privilege discrepancy from orchestrators. This issue affects Linux systems running containerd with CRI checkpoint restore enabled; users not utilizing CRI checkpoint restore are not affected. Patches This bug has been addressed in containerd 2.2.7 and 2.3.4 by disabling checkpoint restore via CreateContainer by default. The feature has been removed entirely in containerd 2.4.0. Users should update to these versions to resolve the issue. Running containers that were restored from untrusted checkpoints should be stopped, deleted, and recreated. Users who rely on restore via the CreateContainer API can re-enable the feature by setting the new enable_experimental_restore_via_create configuration option. However, enabling restore via CreateContainer leaves this vulnerability present, as containerd cannot enforce destination security policy during CRIU process restoration. Workarounds On unpatched versions, containerd does not provide a configuration option to disable checkpoint restore via CreateContainer. Deployments should restrict container creation permissions to trusted users, validate container image registries, or use admission controllers to reject images containing checkpoint data. References CRIU image security Credits The containerd project would like to thank @l2yyd5 and @berkpolatCE for responsibly disclosing this issue in accordance with the containerd security policy. For more information If you have any questions or comments about this advisory: Open an issue in containerd Email us at security@containerd.io To report a security issue in containerd: Report a new vulnerability Email us at security@containerd.io Severity Critical CVE ID No known CVE Weaknesses Weakness CWE-269 Credits @l2yyd5 l2yyd5 Reporter _____________________________________________________________________ containerd CRI plugin: Unbounded I/O draining in ExecSync causes node-level denial of service Moderate samuelkarp published GHSA-7jxh-36q5-gcqv Package github.com/containerd/containerd (Go) Affected versions < 1.7.35 Patched versions 1.7.35 github.com/containerd/containerd/v2 (Go) Affected versions < 2.0.12, >= 2.2.0, < 2.2.8, >= 2.3.0, < 2.3.5 Patched versions 2.3.5, 2.2.8, 2.0.12 Description Impact A bug in containerd's CRI ExecSync implementation allows exec probes and lifecycle hooks with background child processes to keep containerd's stdio-drain goroutines indefinitely blocked. Because the I/O drain phase lacks a default timeout or context cancellation handling, repeated ExecSync invocations (like probes) that include long-lived background processes against a container can cause containerd to leak goroutines and host memory. Over time, this resource exhaustion can cause the containerd daemon to be terminated by the OOM killer, rendering containerd unavailable until it is restarted. This issue affects containerd on Linux systems running with the CRI plugin enabled. Users not using containerd's CRI implementation or not running containers on Linux are not affected. 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 Ensure exec probes and lifecycle hooks do not launch long-lived background child processes. Credits The containerd project would like to thank XlabAI Team of Tencent Xuanwu Lab (xlabai@tencent.com), including Guannan Wang, Zhanpeng Liu, Jiashuo Liang, and Guancheng Li, and @IamwhatIamSY who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy. For more information If you have any questions or comments about this advisory: Open an issue in containerd Email us at security@containerd.io To report a security issue in containerd: Report a new vulnerability Email us at security@containerd.io Severity Moderate CVE ID CVE-2026-53495 Weaknesses Weakness CWE-400 Credits @XlabAITeam XlabAITeam Reporter @keenanwgn keenanwgn Reporter @liangjs liangjs Reporter _____________________________________________________________________ Unpack DoS via repeated opaque whiteouts Moderate samuelkarp published GHSA-rp3h-jf77-q9p4 Package github.com/containerd/containerd (Go) Affected versions < 1.7.35 Patched versions 1.7.35 github.com/containerd/containerd/v2 (Go) Affected versions < 2.0.12, >= 2.2.0, < 2.2.8, >= 2.3.0, < 2.3.5* Patched versions 2.3.5, 2.2.8, 2.0.12 Description 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. For more information If you have any questions or comments about this advisory: Open an issue in containerd Email us at security@containerd.io To report a security issue in containerd: Report a new vulnerability Email us at security@containerd.io Severity Moderate CVE ID No known CVE Weaknesses Weakness CWE-400 Credits @jake-ciolek jake-ciolek Reporter ========================================================= + CERT-RENATER | tel : 01-53-94-20-44 + + 23/25 Rue Daviel | fax : 01-53-94-20-41 + + 75013 Paris | email:cert@support.renater.fr + =========================================================