CVE-2020-15257 | containerd-shim API Exposed to Host Network Containers

containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.

Published: 2020-11-30 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2020-15257 is rated Moderate Risk (46.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 3.24%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-15257

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 12.38% 3.24% -9.14%
2 2026-06-06 13.30% 12.38% -0.93%
3 2026-05-28 13.30%

Full EPSS history (28 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-15257

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.2 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.0 2.7 [email protected]
5.2 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.0 2.7 [email protected]
3.6 2.0 LOW
AV:L/AC:L/Au:N/C:P/I:P/A:N Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
3.9 4.9 [email protected]

Weakness enumeration for CVE-2020-15257

GitHub Security Advisory for CVE-2020-15257

GHSA-36xw-fx78-c5r4 · Severity: medium · Ecosystem: go — containerd-shim API Exposed to Host Network Containers

OS Trackers for CVE-2020-15257

vendor priority summary link
alpine medium CVE-2020-15257: 3 source package rows (containerd, docker, k3s); 31 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 21, open 10. https://security.alpinelinux.org/vuln/CVE-2020-15257
debian not yet assigned CVE-2020-15257 not yet assigned priority: Debian including 2 source packages (containerd, docker.io), 10 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 10. https://security-tracker.debian.org/tracker/CVE-2020-15257
gentoo high CVE-2020-15257: 1 GLSA(s) (202105-33), 1 atom(s) (app-emulation/containerd); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2020-15257
redhat high https://access.redhat.com/security/cve/CVE-2020-15257
suse high https://www.suse.com/security/cve/CVE-2020-15257/
ubuntu medium CVE-2020-15257 medium priority: Ubuntu including 1 source packages (containerd), 6 status rows across 6 suites (bionic, focal, groovy, trusty, upstream, xenial): released 4, DNE 1, pending 1. https://ubuntu.com/security/CVE-2020-15257

Affected software / configurations for CVE-2020-15257

Vendor Product Version Raw CPE
linuxfoundation containerd < 1.3.9 cpe:2.3:a:linuxfoundation:containerd:*:*:*:*:*:*:*:*
linuxfoundation containerd >= 1.4.0, < 1.4.3 cpe:2.3:a:linuxfoundation:containerd:*:*:*:*:*:*:*:*
fedoraproject fedora 33 cpe:2.3:o:fedoraproject:fedora:33:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2020-15257

cvelogic Threat Intelligence