Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-53495

Vulnerability in github.com/containerd/containerd/v2 (CVE-2026-53495)

Summary

Vulnerability in github.com/containerd/containerd/v2 (CVE-2026-53495). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.3.5 or later.

Original description

The description as published by the source.

Impact

A bug in containerd's CRI ExecSync implementation allows exec probes and lifecycle hooks with background child processes to keep containerd's stdio-drain goroutines indefinitely blocked. Because the I/O drain phase lacks a default timeout or context cancellation handling, repeated ExecSync invocations (like probes) that include long-lived background processes against a container can cause containerd to leak goroutines and host memory. Over time, this resource exhaustion can cause the containerd daemon to be terminated by the OOM killer, rendering containerd unavailable until it is restarted. This issue affects containerd on Linux systems running with the CRI plugin enabled. Users not using containerd's CRI implementation or not running containers on Linux are not affected.

Patches

This bug has been fixed in containerd 2.3.5, 2.2.8, 2.0.12, and 1.7.35. Users should update to these versions to resolve the issue.

Workarounds

Ensure exec probes and lifecycle hooks do not launch long-lived background child processes.

Credits

The containerd project would like to thank XlabAI Team of Tencent Xuanwu Lab (xlabai@tencent.com), including Guannan Wang, Zhanpeng Liu, Jiashuo Liang, and Guancheng Li, and @IamwhatIamSY who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.

For more information

If there are any questions or comments…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-53495 has been found in github.com/containerd/containerd/v2.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/containerd/containerd/v2 to 2.3.5 or later.
If unsure, ask your IT team or search "github.com/containerd/containerd/v2 CVE-2026-53495" on the vendor's site.

CVE-2026-53495 (github.com/containerd/containerd/v2) — CWE-400
Patched: 2.3.5 — apply immediately
Workaround: Ensure exec probes and lifecycle hooks do not launch long-lived background child processes.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-400) exists in github.com/containerd/containerd/v2.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/containerd/containerd/v2.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.3.5.

🛡️ Workaround

Workaround: Ensure exec probes and lifecycle hooks do not launch long-lived background child processes.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/containerd/containerd/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/containerd/containerd/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/containerd/containerd/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Ensure exec probes and lifecycle hooks do not launch long-lived background child processes.

    パッチが適用されるまでの応急処置として、Ensure exec probes and lifecycle hooks do not launch long-lived background child processes. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade github.com/containerd/containerd/v2 to 2.3.5

    ステージング環境で 2.3.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/containerd/containerd/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.5"}]}]
go github.com/containerd/containerd
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.35"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details