MediumGHSA-2qjp-425j-52j9CVE-2022-23471GO-2022-1147

containerd CRI stream server vulnerable to host memory exhaustion via terminal

Published 7 Dec 2022 · Updated 10 Sept 2026

Is your project on an affected github.com/containerd/containerd?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<1.5.16
Fixed in
1.5.16
Update to the fixed version for your release line, for example:go get github.com/containerd/containerd@v1.5.16
Affected
>=1.6.0 <1.6.12
Fixed in
1.6.12
Update to the fixed version for your release line, for example:go get github.com/containerd/containerd@v1.6.12

Details

Impact

A bug was found in containerd's CRI implementation where a user can exhaust memory on the host. In the CRI stream server, a goroutine is launched to handle terminal resize events if a TTY is requested. If the user's process fails to launch due to, for example, a faulty command, the goroutine will be stuck waiting to send without a receiver, resulting in a memory leak. Kubernetes and crictl can both be configured to use containerd's CRI implementation and the stream server is used for handling container IO.

Patches

This bug has been fixed in containerd 1.6.12 and 1.5.16. Users should update to these versions to resolve the issue.

Workarounds

Ensure that only trusted images and commands are used and that only trusted users have permissions to execute commands in running containers.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in containerd
  • Email us at [security@containerd.io](mailto:security@containerd.io)

To report a security issue in containerd:

Is GHSA-2qjp-425j-52j9 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/containerd/containerd, and gives you the command that fixes it.

More advisories for github.com/containerd/containerd

  • LowCVE-2026-95837containerd CRI plugin: Checkpoint restore bypasses destination security context in github.com/containerd/containerd · 19 Oct 2026
  • LowCVE-2026-95838containerd: Unpack DoS via repeated opaque whiteouts in github.com/containerd/containerd · 19 Oct 2026
  • MediumCVE-2026-95838containerd: Unpack DoS via repeated opaque whiteouts · 15 Oct 2026
  • LowCVE-2026-53493Containerd has image-pull DoS via crafted OCI index graph amplification in github.com/containerd/containerd · 1 Oct 2026
  • MediumCVE-2026-53493Containerd has image-pull DoS via crafted OCI index graph amplification · 25 Sept 2026
  • LowCVE-2026-53495containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service in github.com/containerd/containerd · 16 Sept 2026
All 48 advisories for github.com/containerd/containerd

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.