GHSA-c9cp-9c75-9v8c: containerd started with non-empty inheritable Linux process capabilities
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).
Published May 14, 2024 · Updated Jul 8, 2024
Affected packages
github.com/containerd/containerd
- Ecosystem
- Go
- Affected
- < 1.5.11
- Fixed in
- 1.5.11
- Check
go list -m github.com/containerd/containerd
github.com/containerd/containerd
- Ecosystem
- Go
- Affected
- >= 1.6.0, < 1.6.2
- Fixed in
- 1.6.2
- Check
go list -m github.com/containerd/containerd
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 [[email protected]](mailto:[email protected]) if you think you’ve found a security bug
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-95838
containerd: Unpack DoS via repeated opaque whiteouts
medium4.6Oct 15, 2026CVE-2026-53493
Containerd has image-pull DoS via crafted OCI index graph amplification
medium6.9Sep 25, 2026CVE-2026-53495
containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service
medium6.8Sep 9, 2026CVE-2026-47262
containerd image-triggered runtime DoS via unbounded group parsing
medium6.9Jun 19, 2026CVE-2026-53488
containerd CRI — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull
high8.7Jun 19, 2026CVE-2026-46680
containerd user ID handling bypass allows runAsNonRoot evasion
high7.8May 21, 2026
