Bug 2549886 (CVE-2026-95837) - CVE-2026-95837 github.com/containerd/containerd: containerd: Privilege escalation via crafted container checkpoint restore
Summary: CVE-2026-95837 github.com/containerd/containerd: containerd: Privilege escala...
Keywords:
Status: NEW
Alias: CVE-2026-95837
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-12 19:51 UTC by OSIDB Bzimport
Modified: 2026-10-16 21:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-12 19:51:28 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.