Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-53495: containerd CRI ExecSync Goroutine Leak Leading to Node-Level Denial of Service

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: azl3 containerd2 2.2.4-8 on Azure Linux 3.0 2.3.4-1; azl3 containerd2 2.3.4-1 on Azure Linux 3.0 2.3.7-1; azl3 moby-containerd-cc 1.7.7-17 on Azure Linux 3.0 1.7.7-19.

Low priority for now. Upgrade to azl3 containerd2 2.2.4-8 on Azure Linux 3.0 2.3.4-1; azl3 containerd2 2.3.4-1 on Azure Linux 3.0 2.3.7-1; azl3 moby-containerd-cc 1.7.7-17 on Azure Linux 3.0 1.7.7-19 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

containerd is an open-source container runtime. Prior to 1.7.35, 2.0.12, 2.2.8, and 2.3.5, containerd on Linux with the CRI plugin enabled can indefinitely block the drainExecSyncIO goroutine in internal/cri/server/container_execsync.go when CRI ExecSync is used by exec probes or lifecycle hooks that launch long-lived background child processes retaining standard input and output pipes. The input and output drain phase has no default timeout and did not stop when the request context was canceled, so repeated ExecSync invocations can accumulate blocked goroutines and host memory. The resulting resource exhaustion can cause the OOM killer to terminate containerd, leaving the container runtime unavailable until restart. Deployments not using containerd's CRI implementation and containers not running on Linux are not affected. This issue is fixed in versions 1.7.35, 2.0.12, 2.2.8, and 2.3.5.

MediumCVSS 6.8 · v4.0—No exploit Fix available
Published
Sep 14, 2026
Updated
Sep 25, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
6.8
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53495

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Using containerd? Add it to your stack and be the first to know about CVEs like this one. (Docker)

Watch new CVEs for containerd

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • containerd containerd

    • < 1.7.35, >= 2.0.0, < 2.0.12, >= 2.2.0, < 2.2.8, >= 2.3.0, < 2.3.5affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.24containerdbefore 2.3.5-r02.3.5-r0
Debian:12containerdfrom 0—
Debian:14containerdbefore 2.1.9+ds1-42.1.9+ds1-4
Gogithub.com/containerd/containerdbefore 1.7.351.7.35
Gogithub.com/containerd/containerd/v2from 2.2.0 · before 2.2.82.2.8
Gogithub.com/containerd/containerd/v2from 2.3.0 · before 2.3.52.3.5
Gogithub.com/containerd/containerd/v2before 2.0.122.0.12
openSUSE:Leap 16.0govulncheck-vulndbbefore 0.0.20260916T180043-160000.1.10.0.20260916T180043-160000.1.1
openSUSE:Leap 16.0haulerbefore 2.1.1-bp160.1.12.1.1-bp160.1.1
openSUSE:Leap 16.0trivybefore 0.74.0-160000.3.10.74.0-160000.3.1
openSUSE:Tumbleweedcontainerdbefore 2.4.2-1.12.4.2-1.1
openSUSE:Tumbleweedhaulerbefore 2.1.0-4.12.1.0-4.1
openSUSE:Tumbleweedtrivybefore 0.75.0-1.10.75.0-1.1
SUSE:Linux Enterprise Server 16.0govulncheck-vulndbbefore 0.0.20260916T180043-160000.1.10.0.20260916T180043-160000.1.1
SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5containerdbefore 1.7.29-16.119.11.7.29-16.119.1
SUSE:Linux Micro 6.1containerdbefore 1.7.29-slfo.1.1_5.11.7.29-slfo.1.1_5.1

Other highest-scoring records for the same primary product.

  • CVE-2026-95837containerd CRI plugin: Checkpoint restore bypasses destination security context
    31Monitor
  • CVE-2026-53493Containerd has image-pull DoS via crafted OCI index graph amplification
    27Monitor
  • CVE-2026-95838containerd: Unpack DoS via repeated opaque whiteouts
    18Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 containerd2 2.2.4-8 on Azure Linux 3.02.3.4-1Microsoft (MSRC)
azl3 containerd2 2.3.4-1 on Azure Linux 3.02.3.7-1 · Release NotesMicrosoft (MSRC)
azl3 moby-containerd-cc 1.7.7-16 on Azure Linux 3.0—Microsoft (MSRC)
azl3 moby-containerd-cc 1.7.7-17 on Azure Linux 3.01.7.7-19 · Release NotesMicrosoft (MSRC)
azl3 moby-containerd-cc 1.7.7-19 on Azure Linux 3.01.7.7-19 · Release NotesMicrosoft (MSRC)
alpine:containerd2.3.5-r0 · Alpine:v3.24Package registry (OSV)
debian:containerd2.1.9+ds1-4 · Debian:14Package registry (OSV)
Go:github.com/containerd/containerd1.7.35Package registry (OSV)
Go:github.com/containerd/containerd/v22.0.12Package registry (OSV)
Go:github.com/containerd/containerd/v22.2.8Package registry (OSV)
Go:github.com/containerd/containerd/v22.3.5Package registry (OSV)
opensuse:containerd2.4.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:govulncheck-vulndb0.0.20260916T180043-160000.1.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:hauler2.1.0-4.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:trivy0.74.0-160000.3.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:trivy0.75.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:containerd1.7.29-slfo.1.1_5.1 · SUSE:Linux Micro 6.1Package registry (OSV)
suse:govulncheck-vulndb0.0.20260916T180043-160000.1.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-5349310 days apartContainerd has image-pull DoS via crafted OCI index graph amplification
    27Monitor
  • CVE-2026-9583828 days apartcontainerd: Unpack DoS via repeated opaque whiteouts
    18Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
function expand(node) {  return node.children.map(expand);}

Fixed

ts
const MAX_DEPTH = 32;function expand(node, depth = 0) {  if (depth > MAX_DEPTH) throw new Error("too deep");  return node.children.map((c) => expand(c, depth + 1));}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records