Live › vulnerability › CVE-2026-95837
Go to dashboardcontainerd's CRI plugin restores container security state (user, capabilities, no_new_privs, seccomp) from a checkpoint instead of the requested container config. An attacker who can create a container from a crafted checkpoint can get a root process with full capabilities and no seccomp filter.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/containerd/containerd | go | all versions | – |
| github.com/containerd/containerd/v2 | go | >= 2.3.0, < 2.3.4 | 2.2.7, 2.3.4 |
Check whether the containerd version is 2.1.0 through 2.2.6 or 2.3.0 through 2.3.3 (run containerd --version); check whether CRI checkpoint restore is used (CreateContainer with a checkpoint image).
2.2.7 or 2.3.4Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-95837")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.