CVE-2026-53489: containerd arbitrary host file read via symlink in CRI checkpoint restore

CVE-2026-53489 · Severity: high · CVSS 4 · Published 2026-07-01

containerd is a core component used to run and manage containers in environments like Kubernetes. A vulnerability in its checkpoint restoration process allows an attacker to use a specially crafted container image to trick the system into reading sensitive files from the underlying host server. This could lead to the exposure of confidential system data or credentials through standard logging commands like 'kubectl logs'.

Technologies: Containerd, github.com/containerd/containerd (Go), github.com/containerd/containerd/v2 (Go). Vendors: Containerd, Go.

Quick answers

Is CVE-2026-53489 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-53489 being exploited in the wild.
How severe is CVE-2026-53489?
High severity, with a CVSS score of 4, published 1 July 2026.
Which products and versions are affected?
Containerd >= 2.1.0, < 2.1.9; >= 2.2.0, < 2.2.5; >= 2.3.0, < 2.3.2; github.com/containerd/containerd (Go) SEMVER:introduced=0; github.com/containerd/containerd/v2 (Go) SEMVER:introduced=2.1.0,fixed=2.1.9, SEMVER:introduced=2.1.0,fixed=2.1.9,introduced=2.2.0,fixed=2.2.5,introduced=2.3.0,fixed=2.3.2.
Is there a fix for CVE-2026-53489?
Yes. github.com/containerd/containerd/v2 (Go): upgrade to 2.1.9, 2.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53489 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-53489?
Check whether you run Containerd, github.com/containerd/containerd (Go) or github.com/containerd/containerd/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/containerd/containerd/v2 (Go): upgrade to 2.1.9, 2.3.2 or later
    go get github.com/containerd/containerd/v2@v2.3.2

Technical details

A symlink following vulnerability (CWE-61) exists in the containerd CRI plugin during the restoration of container logs from a checkpoint image. The plugin fails to validate the path of 'container.log' within the checkpoint, allowing it to be a symbolic link pointing to an arbitrary file on the host filesystem. An attacker who can provide a malicious checkpoint image can exploit this to read sensitive host files when a user or automated system invokes log retrieval commands (e.g., 'kubectl logs'). The issue is local in nature as it requires the ability to influence the checkpoint/image used by the runtime. Patches are available in versions 2.3.2, 2.2.5, and 2.1.9.

Affected products

  • containerd containerd >= 2.1.0, < 2.1.9; >= 2.2.0, < 2.2.5; >= 2.3.0, < 2.3.2

Identifiers

  • CVE-2026-53489
  • GHSA-rgh6-rfwx-v388
  • GO-2026-5622

Timeline

  • 2026-06-18: advisory: GitHub Security Advisory published
  • 2026-07-01: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.