Advisory

GHSA-xhf5-7wjv-pqxp

Also known as: CVE-2026-53488, GO-2026-5758

Summary

containerd CRI — image-config LABEL flows to restart-monitor binary:// logger: host-root command execution from an image pull

Details

Impact
A bug was found in containerd where the CRI plugin propagates labels from an image config (LABEL instruction in Dockerfile) to a container without validation. This may result in executing an arbitrary command on the host, via a plugin that consumes container labels for some operations.

Patches
This bug has been fixed in the following containerd versions:

  • 2.3.2
  • 2.2.5
  • 2.1.9
  • 2.0.10
  • 1.7.33

Users should update to these versions to resolve the issue.

Workarounds
Ensure that only trusted images are used.

Credits
The containerd project would like to thank Anthropic Research, in collaboration with Claude, the GKE Security Team using Gemini, and Robert Prast (@robertprast) for independently discovering and responsibly disclosing this issue in accordance with the containerd security policy.

For more information

If you have any questions or comments about this advisory:

To report a security issue in containerd:

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-06-19 19:35 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 1.7.0, fixed 1.7.33 (semver)

Fixed versions

1.7.33

Fix

github.com/containerd/containerd/v2

Go · All systems

Affected

  • introduced 2.0.0, fixed 2.0.10 (semver)

Fixed versions

2.0.10

Fix

github.com/containerd/containerd/v2

Go · All systems

Affected

  • introduced 2.1.0, fixed 2.1.9 (semver)

Fixed versions

2.1.9

Fix

github.com/containerd/containerd/v2

Go · All systems

Affected

  • introduced 2.2.0, fixed 2.2.5 (semver)

Fixed versions

2.2.5

Fix

github.com/containerd/containerd/v2

Go · All systems

Affected

  • introduced 2.3.0, fixed 2.3.2 (semver)

Fixed versions

2.3.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences