CVE-2026-46680

containerd user ID handling bypass allows runAsNonRoot evasion

HIGH

7.8

CVSS Score

Published: July 1, 2026 at 05:40 PM UTC

Updated: July 3, 2026 at 04:17 AM UTC

2 products affected across 2 vendorsContainerdContainerd

Using containerd by containerd?

Get instant alerts when new vulnerabilities affect containerd - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

containerd is an open-source container runtime. In versions prior to 1.7.32, 2.0.9, 2.2.4 and 2.3.1, containers launched with a numeric User directive that cannot be parsed as a 32-bit integer are incorrectly treated as a username, leading to runAsNonRoot evasion. If a crafted image provides an /etc/passwd file mapping this large numeric string to root, the container ultimately runs as root (UID 0). This allows the Kubernetes runAsNonRoot restriction to be bypassed, causing unexpected behavior for environments that require containers to run as a non-root user. This issue has been fixed in versions 1.7.32, 2.0.9, 2.2.4 and 2.3.1.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Containerd · Linuxfoundation

95%

1.7.27 ≤ v < 1.7.322.0.4 ≤ v < 2.0.92.1.0 ≤ v < 2.2.42.3.0 ≤ v < 2.3.1

Affected range stops below 1.7.32, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.0.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.1, so it looks safe — our inference, not a vendor statement

Containerd · Containerd

60%

v < 1.7.32v < 2.0.9v < 2.2.4v < 2.3.1

Affected range stops below 1.7.32, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.0.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://github.com/containerd/containerd/security/advisories/GHSA-fqw6-gf59-qr4w

References (1)

x_refsource_CONFIRMMitigationVendor Advisory

Source: cverecord

https://github.com/containerd/containerd/security/advisories/GHSA-fqw6-gf59-qr4w

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGH[email protected]

Attack Vector: LOCAL
Complexity: LOW
Privileges: NONE
User Interaction: REQUIRED
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: HIGH
Availability: HIGH

Vector?

Quick Info

StatusANALYZED

CWE

CWE-269

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card