# containerd CRI stream server vulnerable to host memory exhaustion via terminal

Advisory record · `GHSA-2qjp-425j-52j9`

- **Identifiers:** `GHSA-2qjp-425j-52j9` · `CVE-2022-23471` · `GO-2022-1147`
- **State:** Confirmed
- **Severity:** CVSS 5.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-401](https://cwe.mitre.org/data/definitions/401.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 7 Dec 2022
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Dec 2022, 23:23 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.5.16 || >=1.6.0, <1.6.12`; fixed in `1.5.16`, `1.6.12`

## Machine-written summary

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

> The containerd Go package (github.com/containerd/containerd) is vulnerable in versions before 1.5.16 and from 1.6.0 before 1.6.12 through its CRI stream server. A user who runs a command with a TTY requested, and whose process fails to start, can cause a memory leak that exhausts memory on the host. Upgrade to containerd 1.5.16 or 1.6.12; the source lists no other workaround beyond limiting execution to trusted images, commands and users.

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.7 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.011, the 66th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:43 UTC: First seen by agentprime
- 31 Oct 2026, 14:43 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2qjp-425j-52j9)

## Sources

- [GitHub Advisory Database: GHSA-2qjp-425j-52j9](https://github.com/advisories/GHSA-2qjp-425j-52j9)
- [OSV: GHSA-2qjp-425j-52j9](https://osv.dev/vulnerability/GHSA-2qjp-425j-52j9)
- <https://github.com/containerd/containerd/security/advisories/GHSA-2qjp-425j-52j9>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-23471>
- <https://github.com/containerd/containerd/commit/241563be06a3de8b6a849414c4e805b68d3bb295>
- <https://github.com/containerd/containerd/commit/a05d175400b1145e5e6a735a6710579d181e7fb0>
- <https://github.com/containerd/containerd>
- <https://github.com/containerd/containerd/releases/tag/v1.5.16>
- <https://github.com/containerd/containerd/releases/tag/v1.6.12>
- <https://security.gentoo.org/glsa/202401-31>

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 (<https://api.agentprime.io/mcp>), 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: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2qjp-425j-52j9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2qjp-425j-52j9/>. Everything for agents: <https://agentprime.io/llms.txt>.
