CVE-2026-95837

containerd CRI plugin: Checkpoint restore bypasses destination security context

Published Oct 12, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Containerd’s CRI checkpoint restore incorrectly restores the security state from checkpoint data instead of enforcing the requested container configuration. This flaw lets an attacker supply a crafted checkpoint that grants root privileges, full capabilities, no_new_privs, and seccomp state bypasses. The result is a process that runs with root privileges and full capabilities on the host, while the CRI status reports the requested configuration, creating a complete oversight of the container’s security context.

Affected Systems

The vulnerability affects the containerd container runtime, specifically versions from 2.1.0 through the pre‑patch releases of 2.2.x and 2.3.x. The fix is applied in containerd 2.2.7 and 2.3.4, so any older release remains vulnerable. Containers that do not use CRI checkpoint restore are not impacted.

Risk and Exploitability

With a CVSS score of 7.8 the vulnerability is high severity. The EPSS score is less than 1%, and this vulnerability is not listed in the CISA KEV catalog. The likely attack vector requires an attacker to supply a malicious checkpoint file through the CRI interface, which is typically exposed by the kubelet. Successful exploitation gives the attacker root access with all capabilities and bypasses security controls, but it relies on the ability to create or upload a checkpoint. As the issue is wide‑spectrum and exploitable where CRI checkpoint restore is enabled, systems using that feature should prioritise remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade containerd to version 2.2.7, 2.3.4, or any later release where the fix is applied
  • Disable or restrict use of the CRI checkpoint restore feature if it is not required for workloads
  • Limit access to the kubelet CRI endpoint to trusted hosts or services to prevent unauthorized checkpoint uploads

Generated by OpenCVE AI on October 17, 2026 at 08:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-p7v4-vr35-mj6f containerd CRI plugin: Checkpoint restore bypasses destination security context
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Containerd
Containerd containerd
Vendors & Products Containerd
Containerd containerd
Type Values Removed Values Added
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.
Title containerd CRI plugin: Checkpoint restore bypasses destination security context
Weaknesses CWE-269
References
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-266

    Incorrect Privilege Assignment

  • CWE-269

    Improper Privilege Management

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 13, 2026, 5:22 PM
Reserved
Sep 22, 2026, 4:39 PM
Status
Awaiting Analysis
Published
Oct 12, 2026, 8:17 PM
Modified
Oct 16, 2026, 4:00 PM
Severity
Important
Public date
Oct 12, 2026, 7:37 PM