containerd CRI plugin: Checkpoint restore bypasses destination security context
Published 15 Oct 2026 · Updated 19 Oct 2026
Is your project on an affected github.com/containerd/containerd/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.1.0 <2.2.7
- Fixed in
- 2.2.7
go get github.com/containerd/containerd/v2@v2.2.7- Affected
- >=2.3.0 <2.3.4
- Fixed in
- 2.3.4
go get github.com/containerd/containerd/v2@v2.3.4Details
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
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](mailto:security@containerd.io)
To report a security issue in containerd:
- Report a new vulnerability
- Email us at [security@containerd.io](mailto:security@containerd.io)
Is GHSA-p7v4-vr35-mj6f in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/containerd/containerd/v2, and gives you the command that fixes it.
More advisories for github.com/containerd/containerd/v2
- HighCVE-2026-95839containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor · 19 Nov 2026
- LowCVE-2026-95838containerd: Unpack DoS via repeated opaque whiteouts in github.com/containerd/containerd · 19 Oct 2026
- MediumCVE-2026-95838containerd: Unpack DoS via repeated opaque whiteouts · 15 Oct 2026
- LowCVE-2026-53493Containerd has image-pull DoS via crafted OCI index graph amplification in github.com/containerd/containerd · 1 Oct 2026
- MediumCVE-2026-53493Containerd has image-pull DoS via crafted OCI index graph amplification · 25 Sept 2026
- LowCVE-2026-53495containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service in github.com/containerd/containerd · 16 Sept 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.