CVE-2026-95837: containerd CRI plugin Checkpoint Restore Bypasses Destination Security Vulnerability

HIGH
Advisory Identifier: GHSA-p7v4-vr35-mj6f
CVSS 7.8
CWE-269
Published
Advisory Summary

CVE-2026-95837 is a HIGH (CVSS 7.8) checkpoint restore bypasses destination security vulnerability (CWE-269: Improper Privilege Management) affecting containerd CRI plugin libraries in the Go ecosystem. The issue involves checkpoint restore bypasses destination security context. Remediation is available by upgrading affected packages to version 2.2.7, 2.3.4.

CVE-2026-95837 at a Glance

CVE Identifier CVE-2026-95837
GHSA Identifier GHSA-p7v4-vr35-mj6f
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification CWE-269: Improper Privilege Management
Affected Product containerd CRI plugin
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-95837

To remediate this vulnerability, upgrade all affected containerd CRI plugin dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/containerd/containerd/v2 fixed: 2.2.7
Upgrade github.com/containerd/containerd/v2 to 2.2.7
github.com/containerd/containerd/v2 fixed: 2.3.4
Upgrade github.com/containerd/containerd/v2 to 2.3.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/containerd/containerd/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-95837, inspect your project dependencies for containerd CRI plugin:

inspect dependencies for github.com/containerd/containerd/v2

Analyze the terminal output to locate any version of containerd CRI plugin in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.2.7), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. In containerd CRI plugin, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact A vulnerability in containerd's CRI implementation allows a container restored from an untrusted checkpoint via the `CreateContainer` API to bypass the destination security context and execute with elevated privileges. When restoring a container from a checkpoint archive or annotated OCI image, CRIU restores process credentials, Linux capabilities, `no_new_privs`, and seccomp state directly from checkpoint data rather than enforcing the destination CRI `ContainerConfig`. An attacker who can run a container with a crafted checkpoint image can execute processes as root with full capabilities and no enforced seccomp filters despite restrictive security policies requested by the orchestrator. Additionally, containerd's CRI status reporting reflects the requested configuration rather than the actual restored process state, masking the privilege discrepancy from orchestrators. This issue affects Linux systems running containerd with CRI checkpoint restore enabled; users not utilizing CRI checkpoint restore are not affected. ### Patches This bug has been addressed in containerd 2.2.7 and 2.3.4 by disabling checkpoint restore via `CreateContainer` by default. The feature has been removed entirely in containerd 2.4.0. Users should update to these versions to resolve the issue. Running containers that were restored from untrusted checkpoints should be stopped, deleted, and recreated. Users who rely on restore via the `CreateContainer` API can re-enable the feature by setting the new `enable_experimental_restore_via_create` configuration option. However, enabling restore via `CreateContainer` leaves this vulnerability present, as containerd cannot enforce destination security policy during CRIU process restoration. ### Workarounds On unpatched versions, containerd does not provide a configuration option to disable checkpoint restore via `CreateContainer`. Deployments should restrict container creation permissions to trusted users, validate container image registries, or use admission controllers to reject images containing checkpoint data. ### References * [CRIU image security](https://checkpoint-restore.github.io/criu/security/image-security.html) ### Credits The containerd project would like to thank @l2yyd5 and @berkpolatCE for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md). ### For more information If you have any questions or comments about this advisory: * Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose) * Email us at [security@containerd.io](mailto:security@containerd.io) To report a security issue in containerd: * [Report a new vulnerability](https://github.com/containerd/containerd/security/advisories/new) * Email us at [security@containerd.io](mailto:security@containerd.io)

CVE-2026-95837 Affected containerd CRI plugin Versions

2 component(s)
Fixed Versions:
2.2.72.3.4
Product / Package Ecosystem Affected Versions Fixed Version
github.com/containerd/containerd/v2
Go
≥ 2.1.0
< 2.2.7
2.2.7
github.com/containerd/containerd/v2
Go
≥ 2.3.0
< 2.3.4
2.3.4

References

Frequently Asked Questions

What is CVE-2026-95837?
CVE-2026-95837 is a security vulnerability in containerd CRI plugin involving Checkpoint restore bypasses destination security context under CWE-269: Improper Privilege Management.
Which containerd CRI plugin versions are affected?
Affected versions include releases prior to 2.2.7, 2.3.4 across affected packages: github.com/containerd/containerd/v2.
What version fixes CVE-2026-95837?
Upgrading to 2.2.7, 2.3.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/containerd/containerd/v2 affected?
Yes, github.com/containerd/containerd/v2 is affected in releases prior to 2.2.7, 2.3.4. Upgrade your dependency to 2.2.7, 2.3.4 or later.
What is the CVSS score of CVE-2026-95837?
CVE-2026-95837 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-95837?
CVE-2026-95837 is classified under CWE-269: Improper Privilege Management (The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.).
How can I check Go dependencies for CVE-2026-95837?
Run the dependency tree command: 'inspect dependencies for github.com/containerd/containerd/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p7v4-vr35-mj6f",
  "modified" : "2026-10-15T20:21:57Z",
  "published" : "2026-10-15T20:21:57Z",
  "aliases" : [ "CVE-2026-95837" ],
  "summary" : "containerd CRI plugin: Checkpoint restore bypasses destination security context",
  "details" : "### Impact\n\nA vulnerability in containerd's CRI implementation allows a container restored from an untrusted checkpoint via the `CreateContainer` API to bypass the destination security context and execute with elevated privileges. When restoring a container from a checkpoint archive or annotated OCI image, CRIU restores process credentials, Linux capabilities, `no_new_privs`, and seccomp state directly from checkpoint data rather than enforcing the destination CRI `ContainerConfig`. An attacker who can run a container with a crafted checkpoint image can execute processes as root with full capabilities and no enforced seccomp filters despite restrictive security policies requested by the orchestrator. Additionally, containerd's CRI status reporting reflects the requested configuration rather than the actual restored process state, masking the privilege discrepancy from orchestrators. This issue affects Linux systems running containerd with CRI checkpoint restore enabled; users not utilizing CRI checkpoint restore are not affected.\n\n### Patches\n\nThis bug has been addressed in containerd 2.2.7 and 2.3.4 by disabling checkpoint restore via `CreateContainer` by default.  The feature has been removed entirely in containerd 2.4.0. Users should update to these versions to resolve the issue. Running containers that were restored from untrusted checkpoints should be stopped, deleted, and recreated.\n\nUsers who rely on restore via the `CreateContainer` API can re-enable the feature by setting the new `enable_experimental_restore_via_create` configuration option. However, enabling restore via `CreateContainer` leaves this vulnerability present, as containerd cannot enforce destination security policy during CRIU process restoration. \n\n### Workarounds\n\nOn unpatched versions, containerd does not provide a configuration option to disable checkpoint restore via `CreateContainer`. Deployments should restrict container creation permissions to trusted users, validate container image registries, or use admission controllers to reject images containing checkpoint data.\n\n### References\n\n* [CRIU image security](https://checkpoint-restore.github.io/criu/security/image-security.html)\n\n### Credits\n\nThe containerd project would like to thank @l2yyd5 and @berkpolatCE for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md).\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)\n* Email us at [security@containerd.io](mailto:security@containerd.io)\n\nTo report a security issue in containerd:\n* [Report a new vulnerability](https://github.com/containerd/containerd/security/advisories/new)\n* Email us at [security@containerd.io](mailto:security@containerd.io)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/containerd/containerd/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.1.0"
      }, {
        "fixed" : "2.2.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/containerd/containerd/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.3.0"
      }, {
        "fixed" : "2.3.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/containerd/containerd/security/advisories/GHSA-p7v4-vr35-mj6f"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-95837"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/containerd/containerd/pull/13913"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/containerd/containerd/commit/928c03c6898cad95f795300281fdff0dbc55a32f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/containerd/containerd"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-269" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-15T20:21:57Z",
    "nvd_published_at" : "2026-10-12T20:17:10Z"
  }
}