CVE Watch3 jul 2026

CVE-2026-46680

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

CVSS

7.8

Alto

EPSS

0.2%

p13

KEV

—

Exploit Today

0-100

Publicado: 1 jul 2026 · Última mod.: 3 jul 2026 · CWE-269

EPSS · 30d

0.2%EPSS · 30 días0.2%

2026-07-022026-07-17

Descripción técnica

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.

Referencias oficiales

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

CVEs relacionados

CVECVSSEPSSKEVRExplotTítuloVis.

CVE-2026-468179.8 CRÍ

60.3%

KEV—68Oracle E-Business Suite Improper Privilege Management Vulnerability2d CVE-2022-250899.8 CRÍ

96.9%

——29Printix Secure Cloud Print Management through 1.3.1106.0 incorrectly uses Privileged APIs to modify values in HKEY_LOCAL_MACHINE via UITasks.PersistentRegistryData.10d CVE-2026-503437.8 ALT

83.2%

——25Improper privilege management in Microsoft Install Service allows an authorized attacker to elevate privileges locally.3d CVE-2022-262517.2 ALT

75.4%

——23The HTTP interface of Synaman v5.1 and below was discovered to allow authenticated attackers to execute arbitrary code and escalate privileges.10d CVE-2026-463337.1 ALT

69.0%

——21In the Linux kernel, the following vulnerability has been resolved: ptrace: slightly saner 'get_dumpable()' logic The 'dumpability' of a task is fundamentally about the memory image of the task - the concept comes from whether it can core dump or not - and makes no sense when you don't have an associated mm. And almost all users do in fact use it only for the case where the task has a mm pointer. But we have one odd special case: ptrace_may_access() uses 'dumpable' to check various other things entirely independently of the MM (typically explicitly using flags like PTRACE_MODE_READ_FSCREDS). Including for threads that no longer have a VM (and maybe never did, like most kernel threads). It's not what this flag was designed for, but it is what it is. The ptrace code does check that the uid/gid matches, so you do have to be uid-0 to see kernel thread details, but this means that the traditional "drop capabilities" model doesn't make any difference for this all. Make it all make a *bit* more sense by saying that if you don't have a MM pointer, we'll use a cached "last dumpability" flag if the thread ever had a MM (it will be zero for kernel threads since it is never set), and require a proper CAP_SYS_PTRACE capability to override.4d CVE-2022-456088.8 ALT

54.5%

——16An issue was discovered in ThingsBoard 3.4.1, allows low privileged attackers (CUSTOMER_USER) to gain escalated privileges (vertically) and become an Administrator (TENANT_ADMIN) or (SYS_ADMIN) on the web application. It is important to note that in order to accomplish this, the attacker must know the corresponding API's parameter (authority : value).10d