CVE-2026-46680: containerd privilege escalation via numeric User directive parsing error

CVE-2026-46680 · Severity: high · CVSS 3.1 · Published 2026-07-01

containerd is a widely used tool for managing and running software containers, often used within Kubernetes environments. A flaw in how it handles user identification allows specially crafted container images to bypass security settings that are supposed to prevent software from running with administrative (root) privileges. If exploited, an attacker could run a container with full system access, potentially compromising the underlying host or accessing sensitive data.

Technologies: Containerd, github.com/containerd/containerd (Go), github.com/containerd/containerd/v2 (Go). Vendors: Containerd, Go.

Quick answers

Is CVE-2026-46680 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-46680 being exploited in the wild.
How severe is CVE-2026-46680?
High severity, with a CVSS score of 3.1, published 1 July 2026.
Which products and versions are affected?
Containerd < 1.7.32, >= 2.0.4 < 2.0.9, >= 2.0.10 < 2.2.4, >= 2.2.5 < 2.3.1, >= 1.7.27, < 1.7.32; >= 2.0.4, < 2.0.9; >= 2.1.0, < 2.2.4; >= 2.3.0, < 2.3.1; github.com/containerd/containerd (Go) SEMVER:introduced=1.7.27,fixed=1.7.32; github.com/containerd/containerd/v2 (Go) SEMVER:introduced=2.0.4,fixed=2.0.9, SEMVER:introduced=2.0.4,fixed=2.0.9,introduced=2.1.0-beta.0,fixed=2.2.4,introduced=2.3.0-beta.0,fixed=2.3.1.
Is there a fix for CVE-2026-46680?
Yes. github.com/containerd/containerd (Go): upgrade to 1.7.32 or later; github.com/containerd/containerd/v2 (Go): upgrade to 2.0.9, 2.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46680 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-46680?
Check whether you run Containerd, github.com/containerd/containerd (Go) or github.com/containerd/containerd/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/containerd/containerd (Go): upgrade to 1.7.32 or later
    go get github.com/containerd/containerd@v1.7.32
  • github.com/containerd/containerd/v2 (Go): upgrade to 2.0.9, 2.3.1 or later
    go get github.com/containerd/containerd/v2@v2.3.1

Technical details

A vulnerability exists in containerd's handling of the 'User' directive where numeric strings that exceed the capacity of a 32-bit integer are incorrectly parsed as usernames rather than UIDs. An attacker can exploit this by creating a malicious container image with a large numeric User directive and a corresponding entry in /etc/passwd that maps that string to the root user (UID 0). This results in a 'runAsNonRoot' evasion, allowing the container to execute with elevated privileges despite security policies. The issue is reachable via local image import or deployment of untrusted images and has been patched in versions 1.7.32, 2.0.9, 2.2.4, and 2.3.1.

Affected products

  • containerd containerd < 1.7.32, >= 2.0.4 < 2.0.9, >= 2.0.10 < 2.2.4, >= 2.2.5 < 2.3.1

Identifiers

  • CVE-2026-46680
  • GHSA-fqw6-gf59-qr4w
  • GO-2026-5378

Timeline

  • 2026-05-20: advisory: Initial GitHub advisory published
  • 2026-07-01: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.