🛡️ CVE-2026-53488 — containerd
Description
containerd CRI — image-config LABEL flows to restart-monitor binary:// logger: host-root command execution from an image pull
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])
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality high, integrity high, availability high.
Weakness class
CVE-2026-53488 is classified as CWE-20: Improper Input Validation. The application accepts input without checking that it has the expected form, so malformed values reach code that assumes they are well formed.
Affected software
CVE-2026-53488 is recorded against 3 packages.
- containerd (from 2.3.0 up to 2.3.2)
- github.com/containerd/containerd
- github.com/containerd/containerd/v2
Timeline and source
Published on 1 July 2026 and last revised on 3 July 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| containerd | 2.3.0 | 2.3.2 |
| github.com/containerd/containerd | — | — |
| github.com/containerd/containerd/v2 | — | — |
References
Similar Threats
- Unknown BELL-CVE-2026-25680
- Unknown BELL-CVE-2026-25681
- Unknown BELL-CVE-2026-27136
- Unknown BELL-CVE-2026-39821
- Unknown BELL-CVE-2026-39827
More CVE 2026 advisories
Browse all of CVE 2026 in the advisory index.
Site Security Check
Is containerd part of your stack?
CVE-2026-53488 is rated CVSS 8.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.