containerd · containerd · published 2026-07-01

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

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-53489 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 7% of all CVEs. This containerd vulnerability: CVSS 8.2 (v4.0). Fixed upstream in containerd 2.3.2, 2.2.5, 2.1.9, 2.0.10 (+1 more). Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in containerd 2.3.2, 2.2.5, 2.1.9, 2.0.10, 1.7.33.

Patch events

  1. This monthSecurity release

    Container runtimecontainerd

    containerd security releases: 2.3.2, 2.2.5, 2.1.9, 2.0.10, 1.7.33

    Upgrade to 2.3.22.2.52.1.92.0.101.7.33

    Why: Vendor security release for server software (most severe: CVE-2026-53488).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (7th pct)FIRST EPSS v2026.06.15
CVSS base score8.2 (v4.0)
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
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →