GHSA-7jxh-36q5-gcqv: github.com/containerd/containerd/v2 (CVE-2026-53495)

Package	Ecosystem	Affected	Fixed in
github.com/containerd/containerd/v2	Go	<2.0.12 \|\| >=2.2.0, <2.2.8 \|\| >=2.3.0, <2.3.5	2.0.12, 2.2.8, 2.3.5
github.com/containerd/containerd	Go	<1.7.35	1.7.35

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The containerd CRI plugin on Linux is vulnerable in versions below 1.7.35 and in the 2.0.x line below 2.0.12, the 2.2.x line below 2.2.8, and the 2.3.x line below 2.3.5. Repeated ExecSync calls, such as exec probes, whose processes leave long-lived background children can leak goroutines and memory until the containerd daemon is killed by the OOM killer. Upgrade to 1.7.35, 2.0.12, 2.2.8, 2.3.5, or a later release. The source lists a workaround of ensuring exec probes and lifecycle hooks do not start long-lived background processes.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
6.8	Medium	4.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 (GitHub_M)

CISA KEV Not listed.
EPSS 0.0016, the 5th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

4 Sept 2026, 21:22 UTC Published by the maintainers as a GitHub repository advisory
31 Oct 2026, 14:13 UTC First seen by agentprime
31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.