CVSS 4.0
7.3 highCVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NHigh (7.3) in linuxfoundation containerd. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/containerd/containerd 1.7.32.
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:Hgithub.com/containerd/containerd (Go): fixed in 1.7.32github.com/containerd/containerd/v2 (Go): fixed in 2.0.9, 2.2.4, 2.3.1Explain CVE-2026-46680 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46680?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46680?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46680 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| linuxfoundation:containerd | from 1.7.27 before 1.7.32 |
| linuxfoundation:containerd | from 2.0.4 before 2.0.9 |
| linuxfoundation:containerd | from 2.1.0 before 2.2.4 |
| linuxfoundation:containerd | from 2.3.0 before 2.3.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-fqw6-gf59-qr4w | Go | github.com/containerd/containerd | >=1.7.27 <1.7.32 | 1.7.32 |
| GHSA-fqw6-gf59-qr4w | Go | github.com/containerd/containerd/v2 | >=2.0.4 <2.0.9 | 2.0.9 |
| GHSA-fqw6-gf59-qr4w | Go | github.com/containerd/containerd/v2 | >=2.1.0-beta.0 <2.2.4 | 2.2.4 |
| GHSA-fqw6-gf59-qr4w | Go | github.com/containerd/containerd/v2 | >=2.3.0-beta.0 <2.3.1 | 2.3.1 |
| GO-2026-5378 | Go | github.com/containerd/containerd | >=1.7.27 <1.7.32 | 1.7.32 |
| GO-2026-5378 | Go | github.com/containerd/containerd/v2 | >=2.0.4 <2.0.9 >=2.1.0-beta.0 <2.2.4 >=2.3.0-beta.0 <2.3.1 | 2.0.9, 2.2.4, 2.3.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | containerd | no fix listed | DEBIAN-CVE-2026-46680 |
| Debian | 14 | containerd | 2.1.9+ds1-1 | DEBIAN-CVE-2026-46680 |
| Ubuntu | 22.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS and 2 more | containerd | no fix listed | UBUNTU-CVE-2026-46680 |
| Ubuntu | 24.04:LTS, Pro:22.04:LTS | containerd-app | no fix listed | UBUNTU-CVE-2026-46680 |
| Ubuntu | 25.10, 26.10 | containerd, containerd-app, containerd-stable | no fix listed | UBUNTU-CVE-2026-46680 |
| Ubuntu | 26.04:LTS | containerd-app, containerd-stable | no fix listed | UBUNTU-CVE-2026-46680 |
| Ubuntu | Pro:20.04:LTS | containerd, containerd-app | no fix listed | UBUNTU-CVE-2026-46680 |
| Red Hat | hummingbird:1 | trivy | 0:0.72.0-0.1.hum1 | RHSA-2026:35111 |
| SUSE | Linux Enterprise Server 16.1, Linux Enterprise Server for SAP applications 16.1 | docker | 29.7.2_ce-160100.3.1 | SUSE-SU-2026:24740-1 |
| openSUSE | Leap 16.0 | containerd | 1.7.33-160000.1.1 | openSUSE-SU-2026:21213-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
| openSUSE | Leap 16.0 | trivy | 0.71.2-160000.1.1 | openSUSE-SU-2026:21072-1 |
| openSUSE | Leap 16.1 | docker | 29.7.2_ce-160100.3.1 | openSUSE-SU-2026:22345-1 |
| openSUSE | Tumbleweed | containerd | 1.7.33-1.1 | openSUSE-SU-2026:11107-1 |
| openSUSE | Tumbleweed | trivy | 0.71.1-2.1 | openSUSE-SU-2026:11048-1 |
| Alpine | v3.24 | containerd | 2.3.1-r0 | ALPINE-CVE-2026-46680 |
| Azure Linux | 3 | moby-containerd-cc | 1.7.7-16 | AZL-91668 |
| Alpaquita | 23 | containerd | 1.7.32-r0 | BELL-CVE-2026-46680 |
| Alpaquita | 25 | containerd | 2.2.4-r0 | BELL-CVE-2026-46680 |
| Alpaquita | stream | containerd | 2.3.1-r0 | BELL-CVE-2026-46680 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.
Red Hat rates this Important.
Red Hat OpenShift Container Platform and its layered products include the containerd Go library as a build-time dependency for various components. These products do not use containerd as a container runtime; CRI-O is used instead. The vulnerable code path responsible for parsing User directives during container runtime spec generation is not exercised. Therefore, although the containerd library is present in shipped binaries, the vulnerability is not exploitable in the context of Red Hat products.
Enforce a specific numeric runAsUser in the Kubernetes Pod securityContext, which overrides the User directive in the container image and prevents the bypass. Additionally, restrict access to push container images to trusted users only, and validate image provenance before deployment.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | trivy-main-0.72.0-0.1.hum1 | Fixed 2026-07-02 | RHSA-2026:35111 |
| Assisted Installer for Red Hat OpenShift Container Platform 2 | assisted/agent-preinstall-image-builder-rhel9 | Not affected | |
| Assisted Installer for Red Hat OpenShift Container Platform 2 | rhai/assisted-installer-agent-rhel9 | Not affected | |
| Confidential Compute Attestation | openshift-sandboxed-containers/osc-cloud-api-adaptor-rhel9 | Not affected | |
| Confidential Compute Attestation | openshift-sandboxed-containers/osc-monitor-rhel9 | Not affected | |
| Confidential Compute Attestation | openshift-sandboxed-containers/osc-must-gather-rhel9 | Not affected | |
| Confidential Compute Attestation | openshift-sandboxed-containers/osc-podvm-payload-rhel9 | Not affected | |
| Deployment Validation Operator | dvo/deployment-validation-rhel8-operator | Not affected | |
| Gatekeeper 3 | gatekeeper/gatekeeper-rhel9 | Not affected | |
| Kernel Module Management Operator for Red Hat Openshift | kmm/kernel-module-management-must-gather-rhel9 | Not affected | |
| Logging Subsystem for Red Hat OpenShift | openshift-logging/cluster-logging-rhel9-operator | Not affected | |
| Logical Volume Manager Storage | lvms4/lvms-must-gather-rhel9 | Not affected | |
| Machine Deletion Remediation Operator | workload-availability/machine-deletion-remediation-operator-bundle | Not affected | |
| Machine Deletion Remediation Operator | workload-availability/machine-deletion-remediation-rhel9-operator | Not affected | |
| MCP Server for Red Hat OpenShift | openshift-mcp-beta/openshift-mcp-server-rhel9 | Not affected | |
| Migration Toolkit for Containers | rhmtc/openshift-migration-log-reader-rhel8 | Not affected | |
| Migration Toolkit for Containers | rhmtc/openshift-migration-must-gather-rhel8 | Not affected | |
| Migration Toolkit for Virtualization | migration-toolkit-virtualization/mtv-must-gather-rhel8 | Not affected | |
| Migration Toolkit for Virtualization | migration-toolkit-virtualization/mtv-must-gather-rhel9 | Not affected | |
| Migration Toolkit for Virtualization | mtv-candidate/mtv-must-gather-rhel8 | Not affected | |
| 173 more in the JSON and on Red Hat's page. | |||
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-46680.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.