https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-10-20T14:28:05.117148+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/fkie_cve-2026-95837 fkie_cve-2026-95837 2026-10-20T14:28:06.184673+00:00

containerd is an open-source container runtime. From 2.1.0 until 2.2.7 and 2.3.4, containerd's CRI CreateContainer checkpoint restore is vulnerable because CRIU restores process security state from checkpoint data instead of enforcing the destination ContainerConfig. An attacker who can create a container from a crafted checkpoint can supply restored credentials, capabilities, no_new_privs, and seccomp state. The restored process can run as root with full capabilities and no enforced seccomp filters while CRI status reports the requested configuration. Systems that do not use CRI checkpoint restore are not affected. This issue is fixed in versions 2.2.7 and 2.3.4.

 https://vulnerability.circl.lu/vuln/ghsa-p7v4-vr35-mj6f GHSA-p7v4-vr35-mj6f — containerd CRI plugin: Checkpoint restore bypasses destination security context 2026-10-20T14:28:06.184936+00:00

Affected: Go: github.com/containerd/containerd/v2

### 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 s…

 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-95837 UBUNTU-CVE-2026-95837 2026-10-20T14:28:06.185183+00:00

Affected: Ubuntu:Pro:16.04:LTS: containerd, Ubuntu:Pro:18.04:LTS: containerd, Ubuntu:Pro:20.04:LTS: containerd, Ubuntu:Pro:20.04:LTS: containerd-app, Ubuntu:22.04:LTS: containerd, Ubuntu:Pro:22.04:LTS: containerd-app, Ubuntu:24.04:LTS: containerd-app, Ubuntu:Pro:24.04:LTS: containerd, Ubuntu:26.10: containerd, Ubuntu:26.10: containerd-app and 4 more

containerd is an open-source container runtime. From 2.1.0 until 2.2.7 and 2.3.4, containerd's CRI CreateContainer checkpoint restore is vulnerable because CRIU restores process security state from checkpoint data instead of enforcing the destination ContainerConfig. An attacker who can create a container from a crafted checkpoint can supply restored credentials, capabilities, no_new_privs, and seccomp state. The restored process can run as root with full capabilities and no enforced seccomp filters while CRI status reports the requested configuration. Systems that do not use CRI checkpoint restore are not affected. This issue is fixed in versions 2.2.7 and 2.3.4.