CVE-2026-53489Disclosure(linuxfoundation / containerd)

LOWCVSS 6.5 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch linuxfoundation containerd systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-61

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • containerd

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • Peaked 1d ago at 1 mentions (2026-06-19); latest day: 1
  • 2 total mentions across 2 days

Affected systems

Products
containerd

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-06-19: 1Mentions · 2026-07-01: 1Patch / Workaround · 2026-07-01: 1Technical Details · 2026-06-19: 1Technical Details · 2026-07-01: 106-1907-01
Signal classification1 categories
Disclosure
2100.0%
Referenced assets1 URL
Full discourse2 posts
  • Upwind Security MDR@UpwindMDR
    Disclosure

    🚨Critical - containerd CRI Plugin Multiple Vulnerabilities (CVE-2026-50195, CVE-2026-53488, CVE-2026-53492, CVE-2026-53489, CVE-2026-47262) AWS disclosed five flaws in the containerd CRI plugin (v1.7–2.3), the runtime behind EKS, ECS, Fargate, GKE and self-managed Kubernetes. Most are reachable by an attacker who only has permission to create pods on a shared node. The headline bug lets a crafted checkpoint image poison the node's local image cache so other pods unknowingly run the attacker's image — cross-pod code execution. Even nastier: unsanitized image LABEL instructions reach the restart-monitor binary:// logger, giving host-root command execution straight from an image pull, with no checkpoint/restore required. The rest cover CDI annotation smuggling (device/host-mount injection), arbitrary host file read via symlinked log paths, and an image-triggered OOM DoS. 👉Upgrade to containerd 2.3.2 / 2.2.5 / 2.1.9.

    Post summary

    AWS publicly disclosed five critical containerd CRI plugin vulnerabilities affecting multiple cloud platforms, detailing their impact and recommending specific version upgrades.

    00100112
    232 followersView on X
  • DailyCVE@dailycve
    Disclosure

    🔴 containerd, Arbitrary Host File Read via Symlink Following in CRI Checkpoint Restore, #CVE-2026-53489 (High Severity) -DC-Jun2026-501 https://dailycve.com/containerd-arbitrary-host-file-read-via-symlink-following-in-cri-checkpoint-restore-cve-2026-53489-high-severity-dc-jun2026-501/

    Post summary

    The tweet announces CVE‑2026‑53489, detailing an arbitrary host file read vulnerability in containerd’s CRI checkpoint restore, but provides no PoC, exploit code, active exploitation, or patch information.

    0000034
    213 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Applinuxfoundationcontainerd---

Explore more