CVE-2023-25173 containerd supplementary groups are not set up properly
Attackers with container access can bypass group restrictions to gain elevated privileges or execute code due to improper supplementary group setup.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-25173?
CVE-2023-25173 is a medium-severity vulnerability in containerd, published on 16 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
containerd is an open source container runtime. A bug was found in containerd prior to versions 1.6.18 and 1.5.18 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.
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. As a workaround, 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.
Weakness: CWE-863
Which versions are affected by CVE-2023-25173?
5 open source packages ship an affected version, including github.com/containerd/containerd. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/containerd/containerd Go | All versions | 1.5.18, 1.6.18 |
github.com/containerd/containerd Go | All versions | 1.5.18 |
github.com/containerd/containerd Go | All versions | 1.5.18 |
github.com/containerd/containerd Go | From 1.6.0 | 1.6.18 |
github.com/containerd/containerd Go | From 1.6.0 | 1.6.18 |
Linux distribution packages (1)
helm openSUSE:Tumbleweed | All versions | 3.13.0-2.1 |
Products include Linuxfoundation Containerd.
How do I fix CVE-2023-25173?
Upgrade github.com/containerd/containerd to a fixed version for your release line: 1.5.18 or 1.6.18.
Is CVE-2023-25173 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25173 exists.
Other vulnerabilities in containerd
- CVE-2026-53488 containerd CRI — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull
- CVE-2026-53492 containerd CRI checkpoint restore CDI annotation smuggling
- CVE-2026-53489 containerd: Arbitrary host CRI log file read via symlink following in CRI checkpoint restore
- CVE-2025-47290 Containerd vulnerable to host filesystem access during image unpack
- CVE-2026-46680 containerd user ID handling bypass allows runAsNonRoot evasion
Sources
Also known as AZL-13673, CLEANSTART-2025-PN33710, DEBIAN-CVE-2023-25173, GHSA-hmfx-3pcx-653p, GO-2023-1574, UBUNTU-CVE-2023-25173 and 1 more.