Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 9 September 2026.
- Which products and versions are affected?
- Containerd <UNKNOWN>.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network or with local access, in a hosted service.
- Am I affected?
- Check whether you run Containerd or Google Cloud Platform at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in containerd's CRI (Container Runtime Interface) implementation and affects the CreateContainer API when restoring containers from untrusted checkpoints. A container restored from a malicious checkpoint file can bypass the destination security context (such as AppArmor profiles, SELinux policies, or seccomp filters) and execute with elevated privileges. The attack requires the criu binary to be present on the host to enable checkpoint/restore functionality. GKE clusters are not vulnerable by default because GKE node images do not include criu; however, custom installations that add criu tooling become susceptible. No CVE has been assigned yet, but the vulnerability is tracked as GHSA-p7v4-vr35-mj6f.
Affected products
- containerd containerd <UNKNOWN>
Timeline
- 2026-09-09: disclosed