Skip to content

CVE-2026-53492

Linuxfoundation Containerd broken access control

9.6 CRITICALEPSS 0.35%
  1. Published1 Jul 2026

Description

containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Affected products

Linuxfoundation Containerd≥ 2.1.0 < 2.1.9 · ≥ 2.2.0 < 2.2.5 · ≥ 2.3.0 < 2.3.2

Remediation

Fixed in
Linuxfoundation Containerd≥ 2.1.9

Frequently asked

Is CVE-2026-53492 being actively exploited?

CVE-2026-53492 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.35%.

How severe is CVE-2026-53492?

CVE-2026-53492 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.35% probability of exploitation.

Which products are affected by CVE-2026-53492?

Affected products include Linuxfoundation Containerd.

How do I fix CVE-2026-53492?

Upgrade affected software to a fixed version, for example Linuxfoundation Containerd 2.1.9 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-53492 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.