containerd · containerd · published 2026-09-14
CVE-2026-53495containerd CRI ExecSync Goroutine Leak Leading to Node-Level Denial of Service
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-53495 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 5% of all CVEs. This containerd vulnerability: CVSS 6.8 (v4.0). Fixed upstream in containerd 2.3.5, 2.2.8, 2.0.12, 1.7.35. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in containerd 2.3.5, 2.2.8, 2.0.12, 1.7.35.
Patch events
Container runtimecontainerd
containerd security releases: 2.3.5, 2.2.8, 2.0.12, 1.7.35
Upgrade to
2.3.52.2.82.0.121.7.35Why: Vendor security release for server software (most severe: CVE-2026-53495).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (5th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.8 (v4.0)CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- containerd containerd
< 1.7.35(affected)>= 2.0.0, < 2.0.12(affected)>= 2.2.0, < 2.2.8(affected)>= 2.3.0, < 2.3.5(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.