Privilege Escalation in github.com/containerd/containerd (CVE-2026-46680)
Summary
Vulnerability in github.com/containerd/containerd (CVE-2026-46680). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.7.32 or later.
Original description
The description as published by the source.
containerd user ID handling bypass allows runAsNonRoot evasion in github.com/containerd/containerd
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-46680 was discovered in github.com/containerd/containerd.
In plain terms, it is improper privilege management.
Severity is High (CVSS 7.8/10). If exploited, attackers can leak data or disrupt key functionality.
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 CVE-2026-46680".
CVE-2026-46680 (github.com/containerd/containerd). Severity: High / CVSSv3 7.8. Category: CWE-269.
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-46680) in github.com/containerd/containerd. In plain words, it is improper privilege management.
Target versions of github.com/containerd/containerd (see vendor advisory). If running in production, identify exposure immediately.
Severity: High (CVSS 7.8/10). If exploited, attackers can leak data or disrupt key functionality.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-269)
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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/containerd/containerdを grep し、稼働しているサービス・バージョンを把握する。 -
5Apply temporary workaround mitigate
Ensure that only trusted images are used and that only trusted users have permissions to import images.パッチが適用されるまでの応急処置として、Ensure that only trusted images are used and that only trusted users have permissions to import images. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/containerd/containerd to 1.7.32ステージング環境で 1.7.32 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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-46680 containerd Fixed in: 2.3.1-r0
- Ubuntu UBUNTU-CVE-2026-46680 containerd
References
- advisory github.com
- package github.com
- web github.com
- web nvd.nist.gov