CVE-2026-53488: containerd command execution via unvalidated CRI image labels

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

containerd is a widely used industry-standard container runtime that manages the lifecycle of software containers. A vulnerability exists where malicious metadata embedded in a container image can bypass security checks and trigger the execution of unauthorized commands on the underlying host server. This could allow an attacker who can trick a system into pulling a malicious image to gain full control over the host machine, potentially leading to data theft or service disruption.

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

Quick answers

Is CVE-2026-53488 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-53488 being exploited in the wild.
How severe is CVE-2026-53488?
High severity, with a CVSS score of 4, published 1 July 2026.
Which products and versions are affected?
Containerd >= 1.7.0, < 1.7.33; >= 2.0.0, < 2.0.10; >= 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=1.7.0,fixed=1.7.33; github.com/containerd/containerd/v2 (Go) SEMVER:introduced=2.0.0,fixed=2.0.10, SEMVER:introduced=2.0.0,fixed=2.0.10,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-53488?
Yes. github.com/containerd/containerd (Go): upgrade to 1.7.33 or later; github.com/containerd/containerd/v2 (Go): upgrade to 2.0.10, 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-53488 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-53488?
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 (Go): upgrade to 1.7.33 or later
    go get github.com/containerd/containerd@v1.7.33
  • github.com/containerd/containerd/v2 (Go): upgrade to 2.0.10, 2.3.2 or later
    go get github.com/containerd/containerd/v2@v2.3.2

Technical details

A vulnerability in the containerd CRI (Container Runtime Interface) plugin involves improper input validation of labels defined in an image configuration (e.g., the LABEL instruction in a Dockerfile). The plugin propagates these labels to the container without validation. If a secondary plugin or system component consumes these container labels for operations without further sanitization, an attacker can achieve arbitrary command execution on the host. The attack vector is local in the sense that it requires the system to pull and process a malicious image. The issue is addressed in containerd versions 1.7.33, 2.0.10, 2.1.9, 2.2.5, and 2.3.2.

Affected products

  • containerd containerd >= 1.7.0, < 1.7.33; >= 2.0.0, < 2.0.10; >= 2.1.0, < 2.1.9; >= 2.2.0, < 2.2.5; >= 2.3.0, < 2.3.2

Identifiers

  • CVE-2026-53488
  • GHSA-xhf5-7wjv-pqxp
  • GO-2026-5758

Timeline

  • 2026-06-18: advisory: Initial GitHub advisory published
  • 2026-07-01: disclosed: NVD publication date
  • 2026-06-30: patched: Fixes released in multiple versions

References

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