# containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service Advisory record · `GHSA-7jxh-36q5-gcqv` - **Identifiers:** `GHSA-7jxh-36q5-gcqv` · `CVE-2026-53495` · `GO-2026-6444` - **State:** Confirmed - **Severity:** CVSS 6.8 Medium - **Critical:** No - **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) - **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) - **Published:** 9 Sept 2026 - **Updated:** 17 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 9 Sept 2026, 18:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/containerd/containerd/v2` (Go): affected `<2.0.12 || >=2.2.0, <2.2.8 || >=2.3.0, <2.3.5`; fixed in `2.0.12`, `2.2.8`, `2.3.5` - `github.com/containerd/containerd` (Go): affected `<1.7.35`; fixed in `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 - 6.8 Medium, CVSS 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`, from 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](https://github.com/containerd/containerd/security/advisories/GHSA-7jxh-36q5-gcqv) - 31 Oct 2026, 14:13 UTC: First seen by agentprime - 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7jxh-36q5-gcqv) ## Sources - [GitHub Advisory Database: GHSA-7jxh-36q5-gcqv](https://github.com/advisories/GHSA-7jxh-36q5-gcqv) - [OSV: GHSA-7jxh-36q5-gcqv](https://osv.dev/vulnerability/GHSA-7jxh-36q5-gcqv) - - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .