High 8.2Published Jul 1, 2026

CVE-2026-53489containerd: Arbitrary host CRI log file read via symlink following in CRI checkpoint restore

Updated under an hour ago (Oct 27, 2026, 1:23 AM ET)

Does this affect you?

It affects containerd and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for containerd

Exploited in the last 30 days

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.

CVSS: 8.2 HIGH (v4.0, CNA)CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Weakness (CWE): CWE-61
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: GitHub_M
NVD analysis: Analyzed
Record last updated: Jul 2, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

containerd containerd containerd:containerd (from the name)	from 2.1.0, < 2.1.9; from 2.2.0, < 2.2.5; from 2.3.0, < 2.3.2	CNA record
linuxfoundation containerd linuxfoundation:containerd	from 2.1.0 before 2.1.9; from 2.2.0 before 2.2.5; from 2.3.0 before 2.3.2	NVD

References

References

https://github.com/containerd/containerd/security/advisories/GHSA-rgh6-rfwx-v388	x-refsource-confirm, mitigation, vendor-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.