docker: bump buildkit to v0.28.1 for two CVEs

Upgrade github.com/moby/buildkit from v0.18.2 to v0.28.1 and re-vendor
Go dependencies to remediate CVE-2026-33747 and CVE-2026-33748 in
app-containers/docker on cos/release-R121.

Upstream CVE provenance (fixed in github.com/moby/buildkit v0.28.1):
  https://github.com/moby/buildkit/releases/tag/v0.28.1
- CVE-2026-33747 (GHSA-4c29-8rgm-jvjj): fix commit 099cf80f5ebc
  ("executor: validate container IDs centrally") and HTTP source
  hardening 9ce6f62aca06, df4378316f3b.
  https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj
  https://github.com/moby/buildkit/commit/099cf80f5ebc
- CVE-2026-33748 (GHSA-4vrq-3vrq-g6gg): fix commit 45b038cd0b2e
  ("git: normalize and validate subdir paths") and f5462c216098.
  https://github.com/moby/buildkit/security/advisories/GHSA-4vrq-3vrq-g6gg
  https://github.com/moby/buildkit/commit/45b038cd0b2e

Summary of changes:
- Update go.mod and go.sum: bump github.com/moby/buildkit to v0.28.1,
  github.com/containerd/containerd/v2 to v2.2.7,
  github.com/moby/go-archive to v0.3.0, and golang.org/x/net to
  v0.58.0; pin go.etcd.io/etcd v3 modules to v3.5.6 via replace;
  regenerate vendor/ via go mod vendor.
- Adapt builder/builder-next and daemon to buildkit v0.28.1,
  containerd/v2, moby/sys/user, and runtime-spec v1.3.0 (*int64
  LinuxPids.Limit, plus 1-line &limit adjustment in vendored
  containerd v1.7 oci/spec_opts.go), per upstream moby/moby commits
  0aa8fe0bf949, e364e28ec809, ae3a1ac60216, e8c269843c25, c299ba3b38e1,
  3874ca598472, 4b4223a8d42f, f005e1cb7323, 2c66ddf907de, 989e590f525d.

BUG=b/581538059
BUG=b/580969982
TEST=go mod verify; go build/test -mod=vendor; emerge-lakitu docker
RELEASE_NOTE=Fixed CVE-2026-33747 and CVE-2026-33748 in docker.

cos-patch: security-moderate
Change-Id: I8f65c6cd2406d0a4a41e781dd3fecc8a646a3a9c
3320 files changed
tree: 90210e40e9a50af395f216664fbe87307d1207d0
  1. .devcontainer/
  2. .github/
  3. api/
  4. builder/
  5. cli/
  6. client/
  7. cmd/
  8. container/
  9. contrib/
  10. daemon/
  11. distribution/
  12. dockerversion/
  13. docs/
  14. errdefs/
  15. hack/
  16. image/
  17. integration/
  18. integration-cli/
  19. internal/
  20. layer/
  21. libcontainerd/
  22. libnetwork/
  23. man/
  24. oci/
  25. opts/
  26. pkg/
  27. plugin/
  28. profiles/
  29. project/
  30. quota/
  31. reference/
  32. registry/
  33. reports/
  34. restartmanager/
  35. runconfig/
  36. testutil/
  37. vendor/
  38. volume/
  39. .dockerignore
  40. .gitattributes
  41. .gitignore
  42. .golangci.yml
  43. .mailmap
  44. AUTHORS
  45. codecov.yml
  46. CONTRIBUTING.md
  47. docker-bake.hcl
  48. Dockerfile
  49. Dockerfile.simple
  50. Dockerfile.windows
  51. go.mod
  52. go.sum
  53. LICENSE
  54. MAINTAINERS
  55. Makefile
  56. NOTICE
  57. README.md
  58. ROADMAP.md
  59. SECURITY.md
  60. TESTING.md
  61. VENDORING.md
README.md

The Moby Project

Moby Project logo

Moby is an open-source project created by Docker to enable and accelerate software containerization.

It provides a “Lego set” of toolkit components, the framework for assembling them into custom container-based systems, and a place for all container enthusiasts and professionals to experiment and exchange ideas. Components include container build tools, a container registry, orchestration tools, a runtime and more, and these can be used as building blocks in conjunction with other tools and projects.

Principles

Moby is an open project guided by strong principles, aiming to be modular, flexible and without too strong an opinion on user experience. It is open to the community to help set its direction.

  • Modular: the project includes lots of components that have well-defined functions and APIs that work together.
  • Batteries included but swappable: Moby includes enough components to build fully featured container systems, but its modular architecture ensures that most of the components can be swapped by different implementations.
  • Usable security: Moby provides secure defaults without compromising usability.
  • Developer focused: The APIs are intended to be functional and useful to build powerful tools. They are not necessarily intended as end user tools but as components aimed at developers. Documentation and UX is aimed at developers not end users.

Audience

The Moby Project is intended for engineers, integrators and enthusiasts looking to modify, hack, fix, experiment, invent and build systems based on containers. It is not for people looking for a commercially supported system, but for people who want to work and learn with open source code.

Relationship with Docker

The components and tools in the Moby Project are initially the open source components that Docker and the community have built for the Docker Project. New projects can be added if they fit with the community goals. Docker is committed to using Moby as the upstream for the Docker Product. However, other projects are also encouraged to use Moby as an upstream, and to reuse the components in diverse ways, and all these uses will be treated in the same way. External maintainers and contributors are welcomed.

The Moby project is not intended as a location for support or feature requests for Docker products, but as a place for contributors to work on open source code, fix bugs, and make the code more useful. The releases are supported by the maintainers, community and users, on a best efforts basis only. For customers who want enterprise or commercial support, Docker Desktop and Mirantis Container Runtime are the appropriate products for these use cases.


Legal

Brought to you courtesy of our legal counsel. For more context, please see the NOTICE document in this repo.

Use and transfer of Moby may be subject to certain restrictions by the United States and other governments.

It is your responsibility to ensure that your use and/or transfer does not violate applicable laws.

For more information, please see https://www.bis.doc.gov

Licensing

Moby is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.