containerd started with non-empty inheritable Linux process capabilities
Published 14 May 2024 · Updated 8 Jul 2024
Is your project on an affected github.com/containerd/containerd?
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.11
- Fixed in
- 1.5.11
go get github.com/containerd/containerd@v1.5.11- Affected
- >=1.6.0 <1.6.2
- Fixed in
- 1.6.2
go get github.com/containerd/containerd@v1.6.2Details
Impact
A bug was found in containerd where containers were incorrectly started with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set. Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set. Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted.
This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set.
Patches
This bug has been fixed in containerd 1.5.11 and 1.6.2. Users should update to these versions as soon as possible. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset.
This fix changes containerd behavior such that containers are started with a more typical Linux environment. Refer to capabilities(7) for a description of how capabilities work. Note that permitted file capabilities continue to allow for privileges to be raised up to the container's bounding set and that processes may add capabilities to their own inheritable set up to the container's bounding set per the rules described in the manual page. In all cases the container's bounding set provides an upper bound on the capabilities that can be assumed and provides for the container security sandbox.
Workarounds
The entrypoint of a container can be modified to use a utility like capsh(1) to drop inheritable capabilities prior to the primary process starting.
For more information
If you have any questions or comments about this advisory:
- Open an issue
- Email us at [security@containerd.io](mailto:security@containerd.io) if you think you’ve found a security bug
Is GHSA-c9cp-9c75-9v8c 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
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.