MediumGHSA-hmfx-3pcx-653pCVE-2023-25173GO-2023-1574

Supplementary groups are not set up properly in github.com/containerd/containerd

Published 16 Feb 2023 · 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.18
Fixed in
1.5.18
Update to the fixed version for your release line, for example:go get github.com/containerd/containerd@v1.5.18
Affected
>=1.6.0 <1.6.18
Fixed in
1.6.18
Update to the fixed version for your release line, for example:go get github.com/containerd/containerd@v1.6.18

Details

Impact

A bug was found in containerd where supplementary groups are not set up properly inside a container. If an attacker has direct access to a container and manipulates their supplementary group access, they may be able to use supplementary group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive information or gaining the ability to execute code in that container.

Downstream applications that use the containerd client library may be affected as well.

Patches

This bug has been fixed in containerd v1.6.18 and v.1.5.18. Users should update to these versions and recreate containers to resolve this issue. Users who rely on a downstream application that uses containerd's client library should check that application for a separate advisory and instructions.

Workarounds

Ensure that the "USER $USERNAME" Dockerfile instruction is not used. Instead, set the container entrypoint to a value similar to ENTRYPOINT ["su", "-", "user"] to allow su to properly set up supplementary groups.

References

  • https://www.benthamsgaze.org/2022/08/22/vulnerability-in-linux-containers-investigation-and-mitigation/
  • Docker/Moby: CVE-2022-36109, fixed in Docker 20.10.18
  • CRI-O: CVE-2022-2995, fixed in CRI-O 1.25.0
  • Podman: CVE-2022-2989, fixed in Podman 3.0.1 and 4.2.0
  • Buildah: CVE-2022-2990, fixed in Buildah 1.27.1

Note that CVE IDs apply to a particular implementation, even if an issue is common.

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-hmfx-3pcx-653p 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.