| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/containerd/containerd | all versions | |
| github.com/containerd/containerd/v2 | ≥ 2.1.0, < 2.1.9≥ 2.2.0, < 2.2.5≥ 2.3.0, < 2.3.2 | 2.1.92.2.52.3.2 |
| containerd | ≥ 2.1.0, < 2.1.9≥ 2.2.0, < 2.2.5≥ 2.3.0, < 2.3.2 | 2.1.92.2.52.3.2 |
A bug was found in containerd where the CRI plugin restores container.log from a checkpoint image without validating a symlinked path. This could result in reading an arbitrary file on the host via kubectl logs.
This bug has been fixed in the following containerd versions:
Users should update to these versions to resolve the issue.
Ensure that only trusted images and checkpoints are used.
The containerd project would like to thank @gouldnicholas and @davidrxchester, Yuming Zhang and Song Li of Zhejiang University, Sangwon Ryu (@sangwon090), Henry Beberman (@hbeberman) of Microsoft, the GKE Security Team using Gemini, Anthropic Research, in collaboration with Claude, Robert Prast (@robertprast), Kyle Elliott (@kyle-elliott-tob) of Trail of Bits, and Zhenchen Wang (@Plucky923), who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.
If you have any questions or comments about this advisory:
To report a security issue in containerd:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free