CVE-2026-53495

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-77684 (ENISA EUVD) · GHSA-7jxh-36q5-gcqv (GitHub Security Advisories) · GO-2026-6444 (OSV.dev)Source: ENISA EUVD

6.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 9, 2026

Last Modified

September 25, 2026

Advisory Details (9)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

containerd 2.3.5

Patch available: containerd/containerd v2.3.5

https://github.com/containerd/containerd/releases/tag/v2.3.5
GitHub release Patch Available

containerd 2.2.8

Patch available: containerd/containerd v2.2.8

https://github.com/containerd/containerd/releases/tag/v2.2.8
GitHub release Patch Available

containerd 2.0.12

Patch available: containerd/containerd v2.0.12

https://github.com/containerd/containerd/releases/tag/v2.0.12
GitHub commit

commit ff39a972369e (containerd/containerd)

Fix landed in containerd/containerd commit ff39a972369e — awaiting tagged release

https://github.com/containerd/containerd/commit/ff39a972369e2f12fae561a58d658bbf8f2bc318
GitHub commit

commit eebea8c4c912 (containerd/containerd)

Fix landed in containerd/containerd commit eebea8c4c912 — awaiting tagged release

https://github.com/containerd/containerd/commit/eebea8c4c912f44b656c8295c9e6607a19b76650
GitHub commit

commit 9ec55f024041 (containerd/containerd)

Fix landed in containerd/containerd commit 9ec55f024041 — awaiting tagged release

https://github.com/containerd/containerd/commit/9ec55f024041d0641f6d79841e45c8781141ddaa
GitHub commit

commit 5a2a3a759b0d (containerd/containerd)

Fix landed in containerd/containerd commit 5a2a3a759b0d — awaiting tagged release

https://github.com/containerd/containerd/commit/5a2a3a759b0d2ad8c821b33c3afc20890daf6d81
GitHub commit

commit 22ccf4314d1f (containerd/containerd)

Fix landed in containerd/containerd commit 22ccf4314d1f — awaiting tagged release

https://github.com/containerd/containerd/commit/22ccf4314d1fe0834f8e28f10d37d5305ef9880c
GitHub advisoryMentions a patch (unverified)

containerd CRI plugin: Unbounded I/O draining in ExecSync causes node-level denial of service · Advisory · containerd/containerd · GitHub

https://github.com/containerd/containerd/security/advisories/GHSA-7jxh-36q5-gcqv

Vendor Advisories for CVE-2026-53495(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/containerd/containerd @ 1.7.35 (fixes < 1.7.35)—ghsa
gogithub.com/containerd/containerd/v2 @ 2.0.12 (fixes < 2.0.12)—ghsa
gogithub.com/containerd/containerd/v2 @ 2.2.8 (fixes >= 2.2.0, < 2.2.8)—ghsa
gogithub.com/containerd/containerd/v2 @ 2.3.5 (fixes >= 2.3.0, < 2.3.5)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/containerd/containerd—
  • every version up to 1.7.35: fixed in 1.7.35
—
github.com/containerd/containerd/v2—
  • every version up to 2.0.12: fixed in 2.0.12
  • 2.2.0 up to 2.2.8: fixed in 2.2.8
  • 2.3.0 up to 2.3.5: fixed in 2.3.5
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
containerd1.6.20~ds1-1 ... 2.1.9+ds1-5 (45 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
containerd1.7.24~ds1-10 ... 2.1.9+ds1-5 (19 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
containerd1.7.24~ds1-10 ... 2.1.9+ds1-3 (16 versions)
  • every version up to 2.1.9+ds1-4: fixed in 2.1.9+ds1-4
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 110 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 10 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-11-01 07:45 UTCGHSA enrichmentGHSA-7jxh-36q5-gcqv · GitHub severity MODERATE
  11. 2026-11-01 07:45 UTCEG score recompute
  12. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-30 11:55 UTCOSV refresh
  15. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-25 14:20 UTCEG score recompute
  21. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-22 21:49 UTCEG score recompute
  24. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 75 more
  1. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-18 03:31 UTCEG score recompute
  5. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-12 15:57 UTCEG score recompute
  11. 2026-10-11 19:40 UTCEG score recompute
  12. 2026-10-11 16:55 UTCEG score recompute
  13. 2026-10-11 14:19 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-11 07:17 UTCEG score recompute
  16. 2026-10-11 07:17 UTCVendor advisory
  17. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-10 01:21 UTCEG score recompute
  19. 2026-10-10 01:21 UTCVendor advisory
  20. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-08 23:57 UTCEG score recompute
  22. 2026-10-08 23:57 UTCVendor advisory
  23. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-07 12:57 UTCEG score recompute
  26. 2026-10-07 12:57 UTCVendor advisory
  27. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  28. 2026-10-06 11:25 UTCEG score recompute
  29. 2026-10-06 11:25 UTCVendor advisory
  30. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-10-05 10:01 UTCEG score recompute
  32. 2026-10-05 10:01 UTCVendor advisory
  33. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  34. 2026-10-04 08:37 UTCEG score recompute
  35. 2026-10-04 08:37 UTCVendor advisory
  36. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  37. 2026-10-03 07:13 UTCEG score recompute
  38. 2026-10-03 07:13 UTCVendor advisory
  39. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  40. 2026-10-02 05:49 UTCEG score recompute
  41. 2026-10-02 05:49 UTCVendor advisory
  42. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  43. 2026-10-01 03:25 UTCEG score recompute
  44. 2026-10-01 03:25 UTCVendor advisory
  45. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  46. 2026-09-30 02:01 UTCEG score recompute
  47. 2026-09-30 02:01 UTCVendor advisory
  48. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  49. 2026-09-28 20:23 UTCEG score recompute
  50. 2026-09-28 20:23 UTCVendor advisory
  51. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  52. 2026-09-27 17:47 UTCEG score recompute
  53. 2026-09-27 17:47 UTCVendor advisory
  54. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  55. 2026-09-26 16:23 UTCEG score recompute
  56. 2026-09-26 16:23 UTCVendor advisory
  57. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  58. 2026-09-25 14:25 UTCVendor advisory
  59. 2026-09-25 09:43 UTCEG score recompute
  60. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  61. 2026-09-24 08:19 UTCEG score recompute
  62. 2026-09-24 08:19 UTCVendor advisory
  63. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  64. 2026-09-23 06:55 UTCEG score recompute
  65. 2026-09-23 06:55 UTCVendor advisory
  66. 2026-09-22 05:30 UTCEG score recompute
  67. 2026-09-22 05:30 UTCVendor advisory
  68. 2026-09-21 04:06 UTCEG score recompute
  69. 2026-09-21 04:06 UTCVendor advisory
  70. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  71. 2026-09-20 02:42 UTCEG score recompute
  72. 2026-09-20 02:42 UTCVendor advisory
  73. 2026-09-19 01:18 UTCEG score recompute
  74. 2026-09-19 01:18 UTCVendor advisory
  75. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile

Frequently asked(5)

What is CVE-2026-53495?
CVE-2026-53495 is a medium-severity vulnerability; its CVE record was published on September 9, 2026. 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…
When was the CVE record for CVE-2026-53495 published?
The CVE record for CVE-2026-53495 was published on September 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 25, 2026; the record at its source may have been updated since.
Is CVE-2026-53495 actively exploited?
CVE-2026-53495 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53495?
CVE-2026-53495 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53495?
A fix for CVE-2026-53495 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53495 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53495

Explore →

Is Your Infrastructure Affected by CVE-2026-53495?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.