Skip to content

GO-2026-6791 CVE-2026-95837 GHSA-p7v4-vr35-mj6f

containerd CRI plugin: Checkpoint restore bypasses destination security context in github.com/containerd/containerd

High Go
Severity
7.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.11%
Chance of exploitation in the next 30 days. Higher than 1.10% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-269 Improper Privilege Management
Fix
2.2.7
Upgrade github.com/containerd/containerd/v2 to this version or later

Description

containerd CRI plugin: Checkpoint restore bypasses destination security context in github.com/containerd/containerd

Affected versions

Go

PackageVulnerableFixed in
github.com/containerd/containerd
all versions
No fix yet
github.com/containerd/containerd/v2
>= 2.1.0, < 2.2.7
2.2.7
github.com/containerd/containerd/v2
>= 2.3.0, < 2.3.4
2.3.4
github.com/containerd/containerd/v2
>= 2.1.0, < 2.2.7
>= 2.3.0, < 2.3.4
2.2.7
2.3.4

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/containerd/containerd/v2 Go → 2.2.7

go
go get github.com/containerd/containerd/v2@v2.2.7 && go mod tidy

Severity breakdown

CVSS 3.1 7.8

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

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 to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system.
  • Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-rp3h-jf77-q9p4
containerd: Unpack DoS via repeated opaque whiteouts
Medium Also affects github.com/containerd/containerd
GHSA-pg57-6jwg-q645
Containerd has image-pull DoS via crafted OCI index graph amplification
Medium Also affects github.com/containerd/containerd
GHSA-7jxh-36q5-gcqv
containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service
Medium Also affects github.com/containerd/containerd
GO-2026-5064
containerd CRI checkpoint restore CDI annotation smuggling
Critical Also affects github.com/containerd/containerd
GO-2026-5622
Arbitrary host CRI log file read via symlink following in CRI checkpoint restore
Medium Also affects github.com/containerd/containerd
GHSA-xhf5-7wjv-pqxp
containerd CRI — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull
High Also affects github.com/containerd/containerd
GO-2026-5338
containerd: CRI checkpoint import allows local image tag poisoning
Critical Also affects github.com/containerd/containerd
GHSA-jpcc-p29g-p8mq
containerd image-triggered runtime DoS via unbounded group parsing
Medium Also affects github.com/containerd/containerd
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor