Patch Forecast
Yellow warning
Plan into this sprint.

CVE-2026-53493 · GHSA-pg57-6jwg-q645

Containerd has image-pull DoS via crafted OCI index graph amplification

Risk score
57/100
CVSS
6.9 v4.0
Exploit chance (30 days)
0.4%
Published
25 Sep 2026

Open in the live forecast Today's forecast

What to know

What it 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…
Affected
github.com/containerd/containerd/v2 (go) >= 2.0.0, < 2.0.13; github.com/containerd/containerd (go) <= 1.7.35; github.com/containerd/containerd/v2 (go) >= 2.1.0, < 2.2.9; github.com/containerd/containerd/v2 (go) >= 2.3.0, < 2.3.6
Fix
Upgrade github.com/containerd/containerd/v2 to 2.0.13 or 2.2.9 or 2.3.6 or 2.4.1; github.com/containerd/containerd to 1.7.36 (whichever matches your release line) or later.
Exploitation
No known exploitation

Story map

Story map: github.com/containerd/containerd/v2THE FLAWSTHE FIXCVE-2026-53493Containerd has image-pull DoSvia crafted OCI index graphamplificationCVSS 6.9 · EPSS 0%CVE-2026-95837Containerd CRI plugin:Checkpoint restore bypassesdestination security contextCVSS 7.8 · EPSS 0%CVE-2026-95838Containerd: Unpack DoS viarepeated opaque whiteoutsCVSS 4.6 · EPSS 0%Upgrade…1.7.36 · 2.0.13 · 2.2.9 · 2.3.6 ·2.4.1 · 2.2.7or later on your release lineWho is exposedgithub.com/containerd/containerd/v2 (go) >= 2.0.0, < 2.0.13;github.com/containerd/containerd (go) <= 1.7.35;github.com/containerd/contai…YELLOW · PLAN IT INgithub.com/containerd/containerd…containerd is an open-sourcecontainer runtime. Prior toversions 1.7.36, 2.0.13, 2.2.9,2.3.6, and 2.4.1, a crafted OCIindex graph can force very highCPU/memory usage duringPullImage (before container…Where it standsNo known exploitationCONNECTS TOSame weaknessDenial of service (CWE-400)256 other warnings in 30 days →
Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

At a glance

github.com/containerd/containerd/v2: Yellow, plan it in. 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…

The flaws

  • CVE-2026-53493: Containerd has image-pull DoS via crafted OCI index graph amplification (CVSS 6.9 · EPSS 0%)
  • CVE-2026-95837: Containerd CRI plugin: Checkpoint restore bypasses destination security context (CVSS 7.8 · EPSS 0%)
  • CVE-2026-95838: Containerd: Unpack DoS via repeated opaque whiteouts (CVSS 4.6 · EPSS 0%)

The fix

Upgrade github.com/containerd/containerd/v2: 1.7.36 · 2.0.13 · 2.2.9 · 2.3.6 · 2.4.1 · 2.2.7 or later on your release line

Who is exposed: github.com/containerd/containerd/v2 (go) >= 2.0.0, < 2.0.13; github.com/containerd/containerd (go) <= 1.7.35; github.com/containerd/containerd/v2 (go) >= 2.1.0, < 2.2.9; github.com/containerd/containerd/v2 (go) >= 2.3.0, < 2.3.6

Where it stands

  • No known exploitation

Connects to

Why it is Yellow

  • CVSS 6.9 medium
  • On your watchlist: containerd, Go

Affected packages

PackageEcosystemVulnerableFixed in
github.com/containerd/containerd/v2go>= 2.0.0, < 2.0.132.0.13
github.com/containerd/containerdgo<= 1.7.351.7.36
github.com/containerd/containerd/v2go>= 2.1.0, < 2.2.92.2.9
github.com/containerd/containerd/v2go>= 2.3.0, < 2.3.62.3.6
github.com/containerd/containerd/v2go= 2.4.02.4.1

References

Original description

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.

Last activity 25 Sep 2026. Patch Forecast updates every hour.