Vulnerability in github.com/containerd/containerd/v2 (CVE-2026-53492)
Summary
Vulnerability in github.com/containerd/containerd/v2 (CVE-2026-53492). Confidential information can be exposed externally. Mitigation: upgrade to 2.1.9, 2.2.5, 2.3.2 or later.
Original description
The description as published by the source.
containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.
Source: GitHub Security Advisories (Global) 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 weakness called CVE-2026-53492 was discovered in github.com/containerd/containerd/v2.
In plain terms, it is improper input validation.
Severity is Critical (CVSS 9.6/10). If exploited, attackers can fully take over the affected system.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "github.com/containerd/containerd/v2 CVE-2026-53492".
CVE-2026-53492 (github.com/containerd/containerd/v2). Severity: Critical / CVSSv3 9.6. Category: CWE-20.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2026-53492) in github.com/containerd/containerd/v2. In plain words, it is improper input validation.
Target versions of github.com/containerd/containerd/v2 (see vendor advisory). If running in production, identify exposure immediately.
Severity: Critical (CVSS 9.6/10). If exploited, attackers can fully take over the affected system.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-20)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
5Apply temporary workaround mitigate
Users can mitigate this issue by restricting the restoration of containers from untrusted checkpoint images.パッチが適用されるまでの応急処置として、Users can mitigate this issue by restricting the restoration of containers from untrusted checkpoint images. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/containerd/containerd/v2 to 2.3.2ステージング環境で 2.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-53492 containerd Fixed in: 2.3.2-r0
- Debian DEBIAN-CVE-2026-53492 containerd Fixed in: 2.1.9+ds1-1
- Ubuntu UBUNTU-CVE-2026-53492 containerd-app Fixed in: 2.2.1-0ubuntu1~22.04.2
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com