# containerd-shim API Exposed to Host Network Containers Advisory record · `GHSA-36xw-fx78-c5r4` - **Identifiers:** `GHSA-36xw-fx78-c5r4` · `CVE-2020-15257` · `GO-2022-0784` - **State:** Confirmed - **Severity:** CVSS 5.2 Medium - **Critical:** No - **Weakness (CWE):** [CWE-669](https://cwe.mitre.org/data/definitions/669.html) - **Tags:** [CWE-669](https://agentprime.io/advisories/tag/cwe-669.md) - **Published:** 24 May 2021 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 24 May 2021, 17:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/containerd/containerd` (Go): affected `<1.3.9 || >=1.4.0, <1.4.3`; fixed in `1.3.9`, `1.4.3` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > containerd versions before 1.3.9 and from 1.4.0 before 1.4.3 are affected. Containers running in the same network namespace as the containerd-shim, such as host network containers, can connect to the shim's abstract Unix socket and cause new processes to run with elevated privileges, if they have an effective UID of 0 but reduced privileges otherwise. Upgrade to containerd 1.3.9 or 1.4.3, then stop and restart containers started with an older shim, since they stay vulnerable after upgrading. Avoid running untrusted containers in the host network namespace with UID 0. Written 6 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 - 5.2 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.031, the 87th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:46 UTC: First seen by agentprime - 31 Oct 2026, 14:46 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-36xw-fx78-c5r4) ## Sources - [GitHub Advisory Database: GHSA-36xw-fx78-c5r4](https://github.com/advisories/GHSA-36xw-fx78-c5r4) - [OSV: GHSA-36xw-fx78-c5r4](https://osv.dev/vulnerability/GHSA-36xw-fx78-c5r4) - - - - - - - - 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: .