CVE-2026-53495

Medium

Description

containerd is an open-source container runtime. Prior to 1.7.35, 2.0.12, 2.2.8, and 2.3.5, containerd on Linux with the CRI plugin enabled can indefinitely block the drainExecSyncIO goroutine in internal/cri/server/container_execsync.go when CRI ExecSync is used by exec probes or lifecycle hooks that launch long-lived background child processes retaining standard input and output pipes. The input and output drain phase has no default timeout and did not stop when the request context was canceled, so repeated ExecSync invocations can accumulate blocked goroutines and host memory. The resulting resource exhaustion can cause the OOM killer to terminate containerd, leaving the container runtime unavailable until restart. Deployments not using containerd's CRI implementation and containers not running on Linux are not affected. This issue is fixed in versions 1.7.35, 2.0.12, 2.2.8, and 2.3.5.

SeverityMedium
CVSS6.8
Exploit probability—
ProductGithub.com/containerd/containerd/v2
PublishedSep 14, 2026
First seenSep 14, 2026

How to fix

Update
  • github.com/containerd/containerd/v22.0.12, 2.2.8, 2.3.5 or later
  • github.com/containerd/containerd1.7.35 or later

Affected products

ProductAffected versionsFixed in
github.com/containerd/containerd/v2Gov < 2.0.12, 2.2.0 ≤ v < 2.2.8, 2.3.0 ≤ v < 2.3.52.0.12, 2.2.8, 2.3.5
github.com/containerd/containerdGov < 1.7.351.7.35
microsoft azl3_moby-containerd-cc_1.7.7-16No range specified—
microsoft azl3_containerd2_2.2.4-8No range specified—
microsoft azl3_moby-containerd-cc_1.7.7-17No range specified—
microsoft azl3_containerd2_2.3.4-1No range specified—
microsoft azl3_moby-containerd-cc_1.7.7-19No range specified—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.