CVE-2026-53489GO-2026-5622GHSA-RGH6-RFWX-V388
containerd: Arbitrary host CRI log file read via symlink following in CRI checkpoint restore
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.1.9, 2.2.5, 2.3.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a bug 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 issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- containerd containerd
From 2.1.0 · fixed in 2.1.9; From 2.2.0 · fixed in 2.2.5; From 2.3.0 · fixed in 2.3.2
- github.com/containerd/containerdGo
All versions
- github.com/containerd/containerd/v2Go
From 2.1.0 · fixed in 2.1.9; From 2.2.0 · fixed in 2.2.5; From 2.3.0 · fixed in 2.3.2
- github.com/containerd/containerd/v2Go
From 2.1.0 · fixed in 2.1.9
- github.com/containerd/containerd/v2Go
From 2.2.0 · fixed in 2.2.5
- github.com/containerd/containerd/v2Go
From 2.3.0 · fixed in 2.3.2