Answer in brief
CVE-2026-53488 records a Critical severity (CVSS 9.4) vulnerability in containerd CRI — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull in github.com/containerd/containerd. The current sources do not mark it as known exploited. The current feed maps github.com/containerd/containerd (go), github.com/containerd/containerd (go), github.com/containerd/containerd/v2 (go), github.com/containerd/containerd/v2 (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps github.com/containerd/containerd (go), github.com/containerd/containerd (go), github.com/containerd/containerd/v2 (go), github.com/containerd/containerd/v2 (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/containerd/containerdgo | >=1.7.0,<1.7.33 | 1.7.33 |
| github.com/containerd/containerdgo | >=1.7.0 <1.7.33 | 1.7.33 |
| github.com/containerd/containerd/v2go | >=2.0.0,<2.0.10 | 2.0.10 |
| github.com/containerd/containerd/v2go | >=2.1.0,<2.1.9 | 2.1.9 |
| github.com/containerd/containerd/v2go | >=2.2.0,<2.2.5 | 2.2.5 |
| github.com/containerd/containerd/v2go | >=2.3.0,<2.3.2 | 2.3.2 |
| github.com/containerd/containerd/v2go | >=2.0.0 <2.0.10 >=2.1.0 <2.1.9 >=2.2.0 <2.2.5 >=2.3.0 <2.3.2 | 2.0.10, 2.1.9, 2.2.5, 2.3.2 |
| github.com/containerd/containerd/v2go | >=2.0.0 <2.0.10 | 2.0.10 |
| github.com/containerd/containerd/v2go | >=2.1.0 <2.1.9 | 2.1.9 |
| github.com/containerd/containerd/v2go | >=2.2.0 <2.2.5 | 2.2.5 |
| github.com/containerd/containerd/v2go | >=2.3.0 <2.3.2 | 2.3.2 |
Published upstream
Jun 19, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
### 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](https://github.com/containerd/project/blob/main/SECURITY.md). ### For more information If you have any questions or comments about this advisory: * Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose) * Email us at [[email protected]](mailto:[email protected]) To report a security issue in containerd: * [Report a new vulnerability](https://github.com/containerd/containerd/security/advisories/new) * Email us at [[email protected]](mailto:[email protected])
Quoted source text, attributed separately from HOL analysis.