CVE-2026-95837 · GHSA-p7v4-vr35-mj6f

containerd CRI plugin: Checkpoint restore bypasses destination security context

Risk score: 57/100
CVSS: 7.8 v3.1
Exploit chance (30 days): 0.1%
Published: 12 Oct 2026

Open in the live forecast Today's forecast

What to know

What it is: 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 craft…
Affected: github.com/containerd/containerd/v2 (go) >= 2.1.0, < 2.2.7; github.com/containerd/containerd/v2 (go) >= 2.3.0, < 2.3.4
Fix: Upgrade github.com/containerd/containerd/v2 to 2.2.7 or 2.3.4 (whichever matches your release line) or later.
Exploitation: No known exploitation

Why it is Yellow

CVSS 7.8 high
On your watchlist: containerd, Go

Affected packages

Package	Ecosystem	Vulnerable	Fixed in
github.com/containerd/containerd/v2	go	>= 2.1.0, < 2.2.7	2.2.7
github.com/containerd/containerd/v2	go	>= 2.3.0, < 2.3.4	2.3.4

References

Original description

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.

Last activity 12 Oct 2026. Patch Forecast updates every hour.