Vulnerability in containerd-app (UBUNTU-CVE-2026-53492)
Summary
Vulnerability in containerd-app (UBUNTU-CVE-2026-53492). Confidential information can be exposed externally. Mitigation: upgrade to 2.2.1-0ubuntu1~22.04.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: OSV.dev (Open Source Vulnerabilities) OSV
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 UBUNTU-CVE-2026-53492 has been found in containerd-app.
Confidential information can be exposed externally.
What to do: upgrade containerd-app to 2.2.1-0ubuntu1~22.04.2 or later.
If unsure, ask your IT team or search "containerd-app UBUNTU-CVE-2026-53492" on the vendor's site.
UBUNTU-CVE-2026-53492 (containerd-app)
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.2.1-0ubuntu1~22.04.2 — apply immediately
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.
A vulnerability (unclassified) exists in containerd-app.
Check the vendor advisory for the affected versions of containerd-app.
Severity: ?. Confidential information can be exposed externally.
Update to 2.2.1-0ubuntu1~22.04.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'containerd-app' . 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
-
1Identify exposure identify
grep -r 'containerd-app' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
containerd-appを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade containerd-app to 2.2.1-0ubuntu1~22.04.2ステージング環境で 2.2.1-0ubuntu1~22.04.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report github.com