CVE-2026-53488 containerd CRI Label Validation Command Execution Risk
containerd is an open-source container runtime. In versions prior to 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10 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. This issue has been fixed in versions 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10.
Quick answer
containerd should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- < 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
Fixed versions
- 1.7.33
- 2.0.10
- 2.1.9
- 2.2.5
- 2.3.2
How to fix it
containerd is affected by this security issue. The safest fix is to update to the fixed version, then test the site or service again to make sure the risky path is closed.
- Find every place where containerd is installed or used.
- Update to 1.7.33, 2.0.10, 2.1.9, 2.2.5, 2.3.2 or a later vendor-supported version.
- Back up the site or service before changing production systems.
- Apply the update in staging first if possible, then deploy it to production.
- If you cannot update right away, restrict access to the affected feature and monitor logs closely.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is no longer in the affected range.
- Retest the affected page, API, upload, login, chat, container, or network flow.
- Check logs after the change for blocked attempts, crashes, or errors.
- Run a fresh Fixnx scan and save the report.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-53488?
containerd versions listed as affected should be reviewed: < 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.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.