containerd up to 2.4.0 OCI Index Graph resource consumption

Summaryinfo

A vulnerability classified as critical has been found in containerd up to 1.7.35/2.0.12/2.2.8/2.3.5/2.4.0. Impacted is an unknown function of the component OCI Index Graph. Performing a manipulation results in resource consumption. This vulnerability is identified as CVE-2026-53493. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in containerd up to 1.7.35/2.0.12/2.2.8/2.3.5/2.4.0. It has been classified as critical. This affects some unknown processing of the component OCI Index Graph. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:

containerd is an open-source container runtime. Prior to versions 1.7.36, 2.0.13, 2.2.9, 2.3.6, and 2.4.1, a crafted OCI index graph can force very high CPU/memory usage during PullImage (before container start), causing long ContainerCreating stalls and, at larger sizes, node/runtime instability. Versions 1.7.36, 2.0.13, 2.2.9, 2.3.6, and 2.4.1 fix the issue.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-53493 since 06/09/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 1.7.36, 2.0.13, 2.2.9, 2.3.6 or 2.4.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Virtualization Software

Name

• containerd

Version

• 1.7.0
• 1.7.1
• 1.7.2
• 1.7.3
• 1.7.4
• 1.7.5
• 1.7.6
• 1.7.7
• 1.7.8
• 1.7.9
• 1.7.10
• 1.7.11
• 1.7.12
• 1.7.13
• 1.7.14
• 1.7.15
• 1.7.16
• 1.7.17
• 1.7.18
• 1.7.19
• 1.7.20
• 1.7.21
• 1.7.22
• 1.7.23
• 1.7.24
• 1.7.25
• 1.7.26
• 1.7.27
• 1.7.28
• 1.7.29
• 1.7.30
• 1.7.31
• 1.7.32
• 1.7.33
• 1.7.34
• 1.7.35
• 2.0
• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6
• 2.0.7
• 2.0.8
• 2.0.9
• 2.0.10
• 2.0.11
• 2.0.12
• 2.1
• 2.2
• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3
• 2.2.4
• 2.2.5
• 2.2.6
• 2.2.7
• 2.2.8
• 2.3
• 2.3.0
• 2.3.1
• 2.3.2
• 2.3.3
• 2.3.4
• 2.3.5
• 2.4.0

Website

• Product: https://github.com/containerd/containerd/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion