Incorrect Authorization Affecting github.com/containerd/containerd/v2/internal/cri/config package, versions >=2.1.0 <2.2.7>=2.3.0 <2.3.4
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Incorrect Authorization vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMCONTAINERDCONTAINERDV2INTERNALCRICONFIG-20883249
- published13 Oct 2026
- disclosed12 Oct 2026
- creditl2yyd5, Berk Polat
Introduced: 12 Oct 2026
NewCVE-2026-95837 (opens in a new tab)How to fix?
Upgrade github.com/containerd/containerd/v2/internal/cri/config to version 2.2.7, 2.3.4 or higher.
Overview
Affected versions of this package are vulnerable to Incorrect Authorization in the CRImportCheckpoint function in container_checkpoint_linux.go, which restores a container from checkpoint data without enforcing the destination CRI ContainerConfig, so CRIU reinstates process credentials, Linux capabilities, no_new_privs, and seccomp state from the checkpoint itself. An attacker who can run a container from a checkpoint archive or annotated OCI image they control can execute processes as root with full capabilities and no enforced seccomp filter regardless of the restrictive security context the orchestrator requested, and CRI status reporting echoes the requested configuration rather than the restored process state, so the discrepancy is not visible to the orchestrator. This affects Linux systems running with CRI checkpoint restore enabled, and deployments that do not use it are unaffected.
Workaround
This vulnerability can be avoided by restricting container creation to trusted users, validating the registries containers are sourced from, or using an admission controller to reject images carrying checkpoint data.