Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking…

CVSS 3.1 · [email protected] · Secondary 6.1 MEDIUMCVSS 3.1 · [email protected] · Primary 6.1 MEDIUMCVSS 2.0 · [email protected] · Primary 2.6 LOWCheck source for fixed versionsKEV status unknown

Historical advisory recorded 24 Oct 2026 16:17:26 UTC. Read the latest advisory.

nvd · CVE-2020-15157

Published

In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user's username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources. Other container runtimes built on top of containerd but not using the default resolver (such as Docker) are not affected.

Read the publisher's advisory

Affected versions, risk and source history

nvd · CVE-2020-15157

Published

In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the locati…

In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user's username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources. Other container runtimes built on top of containerd but not using the default resolver (such as Docker) are not affected.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-522

Original publisher date fields

published: 2020-10-16T17:15:11.870

lastModified: 2026-06-17T02:56:09.850

13 source CPE criteria · context only
  • cpe:2.3:a:linuxfoundation:containerd:*:*:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:1.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:1.3.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:1.3.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:1.3.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:1.3.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:1.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:1.3.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:1.3.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
  • cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
  • cpe:2.3:o:canonical:ubuntu_linux:20.04:*:*:*:lts:*:*:*
  • cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
16 Oct 2020 17:15:11 UTC
Source modified
17 Jun 2026 02:56:09 UTC
Saved here
24 Oct 2026 16:17:26 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 6.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

CVSS 3.1 · [email protected] · Primary · 6.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

CVSS 2.0 · [email protected] · Primary · 2.6 AV:N/AC:H/Au:N/C:P/I:N/A:N

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 08:00 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current