Vulnerability in containerd-app (UBUNTU-CVE-2026-50195)
Summary
Vulnerability in containerd-app (UBUNTU-CVE-2026-50195). Successful exploitation can lead to full system takeover. 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. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the CRI checkpoint import process where it fails to validate the image references specified within a checkpoint image's configuration. An attacker with permissions to create pods can use a crafted checkpoint image to force containerd to pull a malicious image and assign it an arbitrary local tag, thereby poisoning the node's local image cache. Subsequently, if other pods on the same node attempt to use the poisoned tag with an IfNotPresent (or Never) pull policy, they will unknowingly execute the attacker's malicious image instead of the legitimate one. This can lead to a compromise of the affected pods, allowing the attacker to execute arbitrary code under the victim pod's identity. 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-50195 has been found in containerd-app.
Successful exploitation can lead to full system takeover.
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-50195" on the vendor's site.
UBUNTU-CVE-2026-50195 (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: ?. Successful exploitation can lead to full system takeover.
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