containerd · containerd · published 2026-10-12
CVE-2026-95837containerd CRI plugin: Checkpoint restore bypasses destination security context
Routine No exploitation evidence; EPSS 0.1%.
CVE-2026-95837 is not known to be exploited in the wild. EPSS estimates a 0.1% chance of exploitation in the next 30 days, higher than 1% of all CVEs. This containerd vulnerability: CVSS 7.8 (v3.1), a successful attack gives total control of the component. Fixed upstream in containerd 2.3.4, 2.2.7. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in containerd 2.3.4, 2.2.7.
Patch events
Container runtimecontainerd
containerd security releases: 2.3.4, 2.2.7
Upgrade to
2.3.42.2.7Why: Vendor security release for server software (most severe: CVE-2026-95837).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.1% (1th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.8 (v3.1)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- containerd containerd
>= 2.1.0, < 2.2.7(affected)>= 2.3.0, < 2.3.4(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.