CVE-2026-95837
containerd is an open-source container runtime. From 2.1.0 until …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/containerd/containerd/commit/928c03c6898cad95f795300281fdff0dbc55a32f
- github.com/containerd/containerd/pull/13913
- github.com/containerd/containerd/security/advisories/GHSA-p7v4-vr35-mj6f
- nvd.nist.gov/vuln/detail/CVE-2026-95837
- github.com/advisories/GHSA-p7v4-vr35-mj6f
- nvd.nist.gov/vuln/detail/CVE-2026-95837
- cve.org/CVERecord?id=CVE-2026-95837
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.