Vulnerability · CVE-2026-95837
containerd CRI plugin: Checkpoint restore bypasses destination security context
Published Oct 12, 2026 · catalog updated Oct 15, 2026 · containerd CRI plugin: Checkpoint
Check if you run it
No confirmed exploitation is on record for CVE-2026-95837. EPSS is 0.11%. Act only if a listed version of containerd CRI plugin: Checkpoint is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (containerd CRI plugin: Checkpoint).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.11%
- Remediation
- Version ranges on file
- Affected products
- Go github.com/containerd/containerd/v2 · go github.com/containerd/containerd/v2 · golang github.com · vendor containerd containerd
### Impact A vulnerability in containerd's CRI implementation allows a container restored from an untrusted checkpoint via the 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, , and seccomp state directly from checkpoint data rather than enforcing the destination CRI . 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 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 API can re-enable the feature by setting the new configuration option. However, enabling restore via 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 . Deployments should restrict container creation permissions to trusted users, validate container image registries, or use admission controllers to reject images containing checkpoint data. ### References * [CRIU image security](https://checkpoint-restore.github.io/criu/secu
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Go github.com/containerd/containerd/v22.1.0 → 2.2.7
- Go github.com/containerd/containerd/v22.3.0 → 2.3.4
- go github.com/containerd/containerd/v2>= 2.1.0, < 2.2.7
- go github.com/containerd/containerd/v2>= 2.3.0, < 2.3.4
- go github.com/containerd/containerd/v2>=2.1.0 <2.2.7||>=2.3.0 <2.3.4
- golang github.comversion unspecified
- vendor containerd containerdversion unspecified
How to fix CVE-2026-95837
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-95837. EPSS is 0.11%. Act only if a listed version of containerd CRI plugin: Checkpoint is installed.
Which versions are affected?
Compare what you have installed with 2.1.0 → 2.2.7, 2.3.0 → 2.3.4, >= 2.1.0, < 2.2.7, >= 2.3.0, < 2.3.4, >=2.1.0 <2.2.7||>=2.3.0 <2.3.4. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-269: Improper Privilege Management. EPSS 0.11%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 15, 2026 · GitHub Advisory Database
Detected
### Impact A vulnerability in containerd's CRI implementation allows a container restored from an untrusted checkpoint via the 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, , and seccomp state directly from checkpoint data rather
Oct 15, 2026 · GitHub Advisory Database
Fix available
github.com/containerd/containerd/v2 fixed in 2.2.7; github.com/containerd/containerd/v2 fixed in 2.3.4
Oct 15, 2026 · GitHub Advisory Database
Fix available
github.com/containerd/containerd/v2 fixed in 2.2.7
Oct 15, 2026 · GitHub Advisory Database
Fix available
github.com/containerd/containerd/v2 fixed in 2.3.4
Oct 15, 2026 · GitHub Advisory Database
Updated
### Impact A vulnerability in containerd's CRI implementation allows a container restored from an untrusted checkpoint via the 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, , and seccomp state directly from checkpoint data rather
Sources
- CVE.orgVulnerability recordCVE-2026-95837
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
cve.org - FIRST EPSSExploitation probabilityCVE-2026-95837
30-day exploitation probability 0.1%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-p7v4-vr35-mj6f
containerd CRI plugin: Checkpoint restore bypasses destination security context
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-95837
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 check
advisories.gitlab.com - GitLab Advisory DatabasePackage advisorygo/github.com/containerd/containerd/v2/CVE-2026-95837.yml
A vulnerability in containerd's CRI implementation allows a container + restored from an untrusted checkpoint via the 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, , and seccomp state directly from + checkpoint data rather
gitlab.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-p7v4-vr35-mj6f
containerd CRI plugin: Checkpoint restore bypasses destination security context
osv.dev
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.