Vulnerability in containerd (UBUNTU-CVE-2026-47262)
Summary
Vulnerability in containerd (UBUNTU-CVE-2026-47262). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.2.6-0ubuntu1~16.04.6+esm7 or later.
Original description
The description as published by the source.
containerd is an open-source container runtime. Versions prior to 1.7.33, 2.0.10, 2.1.9, 2.2.5 and 2.3.2, contain a vulnerability that allows a maliciously crafted image to cause a Denial of Service (DoS) condition. When creating a container from this image, memory exhaustion occurs, leading to an Out Of Memory (OOM) kill of the containerd process. This renders the container runtime API unavailable and can disrupt clients such as the Docker Engine or Kubernetes control-plane components. This issue has been fixed in versions 1.7.33, 2.0.10, 2.1.9, 2.2.5 and 2.3.2.
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-47262 has been found in containerd.
Risk of unauthorized operations or information disclosure.
What to do: upgrade containerd to 1.2.6-0ubuntu1~16.04.6+esm7 or later.
If unsure, ask your IT team or search "containerd UBUNTU-CVE-2026-47262" on the vendor's site.
UBUNTU-CVE-2026-47262 (containerd)
Attack vector: local / unauthenticated
Patched: 1.2.6-0ubuntu1~16.04.6+esm7 — 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.
Check the vendor advisory for the affected versions of containerd.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.2.6-0ubuntu1~16.04.6+esm7.
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' . 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
containerdを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade containerd to 1.2.6-0ubuntu1~16.04.6+esm7ステージング環境で 1.2.6-0ubuntu1~16.04.6+esm7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report github.com