Database/Container, Kubernetes & orchestration
runc: `runc exec --cap` created processes with non-empty inheritable capabilities
CVSS 5.9CVE-2022-29162Container, Kubernetes & orchestrationcurated
Impact
runc exec --cap created processes with non-empty inheritable capabilities; unexpected privilege retention
Who can reach it
Any tenant workload
What to do
Replace runc binary; restart affected containers
References
Related entries
- runc: Rootless runc leaves /sys/fs/cgroup writable inside the containerCVE-2023-25809 · runcMedium
- runc: runc can be tricked into creating empty files/directories at arbitrary host locationsCVE-2024-45310 · runcLow
- runc: setupPtmx/setupDev rootfs setup flaw during container rootfs constructionCVE-2026-41579 · runcLow
- runc: Host runc binary overwritten from inside a containerCVE-2019-5736 · runcHigh
- runc: "Leaky Vessels": internal file descriptor leak lets a container process start with cwd in the host filesystemCVE-2024-21626 · runcHigh
- runc: Container filesystem breakout via directory traversal in mount handlingCVE-2021-30465 · runcHigh
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.