CVE-2026-53492
containerd restoration bypasses CDI checks, enabling arbitrary CDI edits on restore.
Is CVE-2026-53492 being exploited?
Not confirmed. CVE-2026-53492 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-53492?
CVE-2026-53492 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53492?
Yes. A fix has been recorded for CVE-2026-53492. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53492 affect?
CVE-2026-53492 affects containerd (versions < 2.3.2, <2.2.5, <2.1.9), Kubernetes environments using containerd CRI. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53492?
Upgrade to fixed versions: 2.3.2, 2.2.5, or 2.1.9+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution/host escape via injected CDI edits during container restore; requires CDI enabled and matching host spec.
Immediate action required
- affected>= 2.1.0 and < 2.1.9
- affected>= 2.2.0 and < 2.2.5
- affected>= 2.3.0 and < 2.3.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.