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: * Report a new vulnerability * Email us at security@containerd.io
{
"github_reviewed_at": "2026-06-19T19:35:36Z",
"cwe_ids": [
"CWE-61"
],
"severity": "HIGH",
"nvd_published_at": null,
"github_reviewed": true
}