- Update Docker Scan to [v0.21.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.21.0).
- Update containerd (`containerd.io` package) to [v1.6.9](https://github.com/containerd/containerd/releases/tag/v1.6.9).
- Update bundled BuildKit version to fix `output clipped, log limit 1MiB reached` errors [moby/moby#44339](https://github.com/moby/moby/pull/44339).

### Bug fixes and enhancements
- Remove experimental gate for `--platform` in bash completion [docker/cli#3824](https://github.com/docker/cli/pull/3824).
- Fix an `Invalid standard handle identifier` panic when  registering the Docker Engine as a service from a legacy CLI on Windows [moby/moby#44326](https://github.com/moby/moby/pull/44326).
- Fix running Git commands in Cygwin on Windows [moby/moby#44332](https://github.com/moby/moby/pull/44332).

## 20.10.20
{{< release-date date="2022-10-18" >}}

This release of Docker Engine contains partial mitigations for a Git vulnerability
([CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253)),
and has updated handling of `image:tag@digest` image references.

The Git vulnerability allows a maliciously crafted Git repository, when used as a
build context, to copy arbitrary filesystem paths into resulting containers/images;
this can occur in both the daemon, and in API clients, depending on the versions and
tools in use.

The mitigations available in this release and in other consumers of the daemon API
are partial and only protect users who build a Git URL context (e.g. `git+protocol://`).
As the vulnerability could still be exploited by manually run Git commands that interact
with and check out submodules, users should immediately upgrade to a patched version of
Git to protect against this vulnerability. Further details are available from the GitHub
blog (["Git security vulnerabilities announced"](https://github.blog/2022-10-18-git-security-vulnerabilities-announced/)).

### Updates

- Update Docker Compose to [v2.12.0](https://github.com/docker/compose/releases/tag/v2.12.0).
- Updated handling of `image:tag@digest` references. When pulling an image using
  the `image:tag@digest` ("pull by digest"), image resolution happens through
  the content-addressable digest and the `image` and `tag` are not used. While
  this is expected, this could lead to confusing behavior, and could potentially
  be exploited through social engineering to run an image that is already present
  in the local image store. Docker now checks if the digest matches the repository
  name used to pull the image, and otherwise will produce an error.
- Updated handling of `image:tag@digest` references. Refer to the "Daemon" section
  above for details.

### Bug fixes and enhancements

- Added a mitigation for [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253),
  when using the classic Builder with a Git URL as the build context.
- Added a mitigation to the classic Builder and updated BuildKit to [v0.8.3-31-gc0149372](https://github.com/moby/buildkit/commit/c014937225cba29cfb1d5161fd134316c0e9bdaa),
  for [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253).

## 20.10.19
{{< release-date date="2022-10-14" >}}

This release of Docker Engine comes with some bug-fixes, and an updated version
of Docker Compose.

### Updates

- Update Docker Compose to [v2.11.2](https://github.com/docker/compose/releases/tag/v2.11.2).
- Update Go runtime to [1.18.7](https://go.dev/doc/devel/release#go1.18.minor),
  which contains fixes for [CVE-2022-2879](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2879),
  [CVE-2022-2880](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2880),
  and [CVE-2022-41715](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41715).

### Bug fixes and enhancements

- Fix an issue that could result in a panic during `docker builder prune` or
  `docker system prune` [moby/moby#44122](https://github.com/moby/moby/pull/44122).
- Fix a bug where using `docker volume prune` would remove volumes that were