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

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

Summary

Vulnerability in github.com/containerd/containerd/v2 (CVE-2026-53493). Risk of unauthorized operations or information disclosure. Exploitable via PullImage. Mitigation: upgrade to 2.4.1 or later.

Original description

The description as published by the source.

Impact

A vulnerability exists in containerd's image pull handlers where a crafted OCI image index containing deeply nested or heavily fanned-out descriptor graphs can cause unbounded CPU and memory consumption. During the PullImage operation, the recursive traversal and processing of child descriptors lack sufficient depth and breadth limits, and fail to adequately deduplicate identical descriptors. This unbounded traversal leads to excessive resource allocation.

Consequently, pulling a malicious image reference can result in prolonged stalls during container creation and significant resource pressure on the host system. This issue occurs entirely during the image pull phase, prior to any container execution.

Patches

This bug has been fixed in containerd 2.4.1, 2.3.6, 2.2.9, 2.0.13, and 1.7.36. Users should update to these versions to resolve the issue.

Workarounds

There are no known workarounds for this issue. Users are advised to only pull trusted images from known registries until the patch can be applied.

Credits

The containerd project would like to thank Jakub Ciolek at ElevenLabs and @jlgore who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.

For more information

If you have any questions or comments about this advisory:

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-53493 has been found in github.com/containerd/containerd/v2.
Attackers can target a specific entry point like PullImage over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/containerd/containerd/v2 to 2.4.1 or later.
If unsure, ask your IT team or search "github.com/containerd/containerd/v2 CVE-2026-53493" on the vendor's site.

CVE-2026-53493 (github.com/containerd/containerd/v2) — CWE-400
Attack surface: PullImage
Patched: 2.4.1 — apply immediately
Workaround: There are no known workarounds for this issue.
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. Attackers reach the vulnerable code path via PullImage.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/containerd/containerd/v2. Attack surface: PullImage.

🔥 Severity

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

🔧 How to fix

Update to 2.4.1.

🛡️ Workaround

Workaround: There are no known workarounds for this issue.

🔍 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 
    There are no known workarounds for this issue.

    パッチが適用されるまでの応急処置として、There are no known workarounds for this issue. を実施。回避策の副作用 (機能低下) を確認した上で。

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

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

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

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

Affected packages

go github.com/containerd/containerd/v2
[{"type":"SEMVER","events":[{"introduced":"2.4.0"},{"fixed":"2.4.1"}]}]
go github.com/containerd/containerd
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.36"}]}]

References

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