runc Container Escapes: Three Mount-Race CVEs Fixed
Not remotely exploitable and not seen in attacks, but anyone who runs or builds images they do not fully trust (CI runners, multi-tenant clusters) should roll out patched runc this week.
Must act: Operators of shared CI/build runners, multi-tenant Kubernetes, and any host that runs third-party images or untrusted Dockerfiles on runc below 1.2.8/1.3.3.
Can relax: Single-tenant hosts that only run images you build from reviewed sources, and rootless or user-namespaced setups, where impact is largely neutralized; patch on the normal cycle.
- Check the runtime on each node: runc --version (or docker info | grep -i runc; containerd ships its own runc binary)
- Upgrade runc to 1.2.8, 1.3.3 or later via your distro, Docker Engine, containerd or managed-Kubernetes node image updates
- Prioritize CI runners, BuildKit/buildx builders and multi-tenant nodes that run untrusted images or Dockerfiles