CVE-2026-53489
Received Received - Intake

Symlink Path Traversal in containerd CRI Plugin

Vulnerability report for CVE-2026-53489, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-01

Last updated on: 2026-07-01

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-01
Last Modified
2026-07-01
Generated
2026-07-02
AI Q&A
2026-07-01
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
containerd containerd to 2.3.2 (exc)
containerd containerd to 2.2.5 (exc)
containerd containerd to 2.1.9 (exc)
containerd containerd From 2.1.0 (inc) to 2.1.9 (exc)
containerd containerd From 2.2.0 (inc) to 2.2.5 (exc)
containerd containerd From 2.3.0 (inc) to 2.3.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-61 The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-53489 is a vulnerability in containerd, an open-source container runtime. The issue occurs because the CRI plugin restores container.log from a checkpoint image without properly validating symlinked paths. This flaw allows an attacker to read arbitrary files on the host system by exploiting symlink following when using kubectl logs.

Impact Analysis

This vulnerability can impact you by allowing an attacker to read sensitive or arbitrary files on the host system through the container runtime's logging mechanism. This could lead to exposure of confidential information or system files, potentially compromising the security of your host environment.

Detection Guidance

This vulnerability involves the CRI plugin in containerd restoring container.log from a checkpoint image without validating symlinked paths, which can be exploited via kubectl logs to read arbitrary host files.

To detect if your system is vulnerable, first check the version of containerd running on your system. Vulnerable versions are 2.1.0 to 2.1.8, 2.2.0 to 2.2.4, and 2.3.0 to 2.3.1.

  • Run the command: `containerd --version` or `containerd -v` to determine the installed version.
  • Check logs for unusual or unexpected file reads when using `kubectl logs` on containers managed by containerd.
  • Audit checkpoint images and container logs for symlinked paths that could point outside the container filesystem.
Mitigation Strategies

The primary mitigation is to upgrade containerd to a patched version where this vulnerability is fixed.

  • Update containerd to version 2.3.2, 2.2.5, or 2.1.9 or later.
  • As a temporary measure, only use trusted images and checkpoints to reduce the risk of exploitation.
Compliance Impact

This vulnerability allows an attacker to read arbitrary files on the host system via symlink following in the containerd CRI checkpoint restore functionality. Such unauthorized access to sensitive files could lead to exposure of personal or protected data.

Exposure of sensitive data through this vulnerability may impact compliance with data protection regulations such as GDPR and HIPAA, which require strict controls on access to personal and health information.

Mitigating this risk by updating to patched versions or restricting usage to trusted images is essential to maintain compliance and reduce the risk of unauthorized data disclosure.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53489. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart