← Back
CVE-2026-46680
high
CVSS 7.8
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. Exploitable via ``User``. Mitigation: upgrade to `1.7.32` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-46680** has been found in github.com/containerd/containerd.
Attackers can target a specific entry point like ``User`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade github.com/containerd/containerd to **1.7.32** or later.
If unsure, ask your IT team or search "github.com/containerd/containerd CVE-2026-46680" on the vendor's site.
CVE-2026-46680 (github.com/containerd/containerd) — CWE-269 / CVSS v3 7.8
Attack vector: local / unauthenticated
Attack surface: `User` / `runAsNonRoot` / `runAsUser` / `securityContext`
Patched: `1.7.32` — apply immediately
Workaround: Ensure that only trusted images are used and that only trusted users have permissions to import images.
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.
❓ What is the problem
**A vulnerability** (CWE-269) exists in github.com/containerd/containerd. Attackers reach the vulnerable code path via ``User`` without authentication.
📍 Affected scope
github.com/containerd/containerd — . Attack surface: `User` / `runAsNonRoot` / `runAsUser` / `securityContext`.
🔥 Severity
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.7.32**.
🛡️ Workaround
Workaround: Ensure that only trusted images are used and that only trusted users have permissions to import images.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/containerd/containerd' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
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
go
github.com/containerd/containerd
[{"type":"SEMVER","events":[{"introduced":"1.7.27"},{"fixed":"1.7.32"}]}]
go
github.com/containerd/containerd/v2
[{"type":"SEMVER","events":[{"introduced":"2.3.0-beta.0"},{"fixed":"2.3.1"}]}]