github.com/moby/buildkit

Version	Released
`v0.32.0` minor	Jul 27, 2026
`v0.32.0-rc2` pre	Jul 27, 2026
`v0.31.2` patch	Jul 16, 2026
`v0.31.0` minor	Jun 16, 2026
`v0.31.0-rc2` pre	Jun 12, 2026
`v0.31.0-rc1` pre	Jun 10, 2026
`v0.30.0` minor	May 13, 2026
`v0.30.0-rc2` pre	May 11, 2026
`v0.29.0` minor	Mar 31, 2026
`v0.28.0` minor 2 CVEs	Mar 03, 2026
`v0.28.0-rc2` pre 2 CVEs	Feb 26, 2026
`v0.27.0-rc1` pre 2 CVEs	Jan 14, 2026
`v0.26.2` minor 2 CVEs	Nov 20, 2025
`v0.25.2` minor 2 CVEs	Nov 05, 2025
`v0.24.0-rc2` pre 2 CVEs	Aug 29, 2025
`v0.23.0-rc2` pre 2 CVEs	Jun 16, 2025
`v0.23.0-rc1` pre 2 CVEs	Jun 11, 2025
`v0.21.0-rc2` pre 2 CVEs	Apr 11, 2025
`v0.20.0-rc3` pre 2 CVEs	Feb 18, 2025
`v0.19.0-rc1` pre 2 CVEs	Jan 14, 2025
`v0.17.2` patch 2 CVEs	Nov 22, 2024
`v0.18.0-rc1` pre 2 CVEs	Nov 21, 2024
`v0.17.0` minor 2 CVEs	Oct 29, 2024
`v0.16.0` minor 2 CVEs	Sep 10, 2024
`v0.16.0-rc2` pre 2 CVEs	Sep 09, 2024
`v0.15.1` minor 2 CVEs	Jul 25, 2024
`v0.14.0-rc2` pre 2 CVEs	Jun 06, 2024
`v0.13.0` minor 2 CVEs	Mar 05, 2024
`v0.13.0-rc2` pre 2 CVEs	Feb 24, 2024
`v0.13.0-rc1` pre 2 CVEs	Feb 15, 2024
`v0.13.0-beta3` pre 2 CVEs	Jan 31, 2024
`v0.13.0-beta2` pre 2 CVEs	Jan 30, 2024
`v0.12.4` patch 6 CVEs	Nov 29, 2023
`v0.12.1` minor 6 CVEs	Aug 02, 2023
`v0.11.4` patch 6 CVEs	Mar 06, 2023
`v0.11.3` patch 7 CVEs	Feb 13, 2023
`v0.11.1` minor 7 CVEs	Jan 17, 2023
`v0.11.0-rc4` pre 7 CVEs	Jan 06, 2023
`v0.11.0-rc2` pre 7 CVEs	Dec 13, 2022
`v0.10.6` patch 7 CVEs	Nov 10, 2022
`v0.10.4` minor 7 CVEs	Aug 22, 2022
`v0.10.0-rc1` pre 6 CVEs	Feb 14, 2022
`v0.9.1` minor 6 CVEs	Oct 04, 2021
`v0.9.0-rc2` pre 6 CVEs	Jul 16, 2021
`v0.8.2` minor 6 CVEs	Feb 25, 2021
`v0.8.0-rc3` pre 6 CVEs	Nov 26, 2020
`v0.7.1` minor 6 CVEs	Apr 16, 2020
`v0.6.4` patch 6 CVEs	Feb 21, 2020
`v0.6.3` minor 6 CVEs	Nov 13, 2019
`v0.3.2` initial 6 CVEs	Oct 31, 2018

v0.32.0 minor

Jul 27, 2026

v0.32.0-rc2 pre

Jul 27, 2026

v0.31.2 patch

Jul 16, 2026

v0.31.0 minor

Jun 16, 2026

v0.31.0-rc2 pre

Jun 12, 2026

v0.31.0-rc1 pre

Jun 10, 2026

v0.30.0 minor

May 13, 2026

v0.30.0-rc2 pre

May 11, 2026

v0.29.0 minor

Mar 31, 2026

v0.28.0 minor

2 CVEs

Mar 03, 2026

v0.28.0-rc2 pre

2 CVEs

Feb 26, 2026

v0.27.0-rc1 pre

2 CVEs

Jan 14, 2026

v0.26.2 minor

2 CVEs

Nov 20, 2025

v0.25.2 minor

2 CVEs

Nov 05, 2025

v0.24.0-rc2 pre

2 CVEs

Aug 29, 2025

v0.23.0-rc2 pre

2 CVEs

Jun 16, 2025

v0.23.0-rc1 pre

2 CVEs

Jun 11, 2025

v0.21.0-rc2 pre

2 CVEs

Apr 11, 2025

v0.20.0-rc3 pre

2 CVEs

Feb 18, 2025

v0.19.0-rc1 pre

2 CVEs

Jan 14, 2025

v0.17.2 patch

2 CVEs

Nov 22, 2024

v0.18.0-rc1 pre

2 CVEs

Nov 21, 2024

v0.17.0 minor

2 CVEs

Oct 29, 2024

v0.16.0 minor

2 CVEs

Sep 10, 2024

v0.16.0-rc2 pre

2 CVEs

Sep 09, 2024

v0.15.1 minor

2 CVEs

Jul 25, 2024

v0.14.0-rc2 pre

2 CVEs

Jun 06, 2024

v0.13.0 minor

2 CVEs

Mar 05, 2024

v0.13.0-rc2 pre

2 CVEs

Feb 24, 2024

v0.13.0-rc1 pre

2 CVEs

Feb 15, 2024

v0.13.0-beta3 pre

2 CVEs

Jan 31, 2024

v0.13.0-beta2 pre

2 CVEs

Jan 30, 2024

v0.12.4 patch

6 CVEs

Nov 29, 2023

v0.12.1 minor

6 CVEs

Aug 02, 2023

v0.11.4 patch

6 CVEs

Mar 06, 2023

v0.11.3 patch

7 CVEs

CVE-2026-33747 GO-2026-4858 GHSA-4c29-8rgm-jvjj Mar 27, 2026

BuildKit's Malicious frontend can cause file escape outside of storage root in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2026-33748 GO-2026-4859 GHSA-4vrq-3vrq-g6gg Mar 27, 2026

BuildKit Git URL subdir component can cause access to restricted files in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2024-23651 GO-2024-2493 GHSA-m3r6-h7wv-7xxv Feb 13, 2024

Host system file access in github.com/moby/buildkit

Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container.

Fixed in


          0.12.5

References

https://github.com/moby/buildkit/pull/4604

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23650 GO-2024-2492 GHSA-9p26-698r-w4hx Feb 12, 2024

Panic in github.com/moby/buildkit

A malicious BuildKit client or frontend could craft a request that could lead to a BuildKit daemon crashing with a panic.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23652 GO-2024-2494 GHSA-4v98-7qmw-rqr8 Feb 12, 2024

Host system modification in github.com/moby/buildkit

A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23653 GO-2024-2497 GHSA-wr6v-9f75-vh2g Feb 07, 2024

Privilege escalation in github.com/moby/buildkit

BuildKit provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special security.insecure entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2023-26054 GHSA-gc89-7gcr-jxqc Mar 07, 2023

Buildkit credentials inlined to Git URLs could end up in provenance attestation

6.5 / 10

Medium

Network Low None Required Unchanged High None None

When the user sends a build request that contains a Git URL that contains credentials and the build creates a provenance attestation describing that build, these credentials could be visible from the provenance attestation.

Git URL can be passed in two ways:

Invoking build directly from a URL with credentials.

buildctl build --frontend dockerfile.v0 --context https://<credentials>@url/repo.git

Equivalent in docker buildx would be

docker buildx build https://<credentials>@url/repo.git

If the client sends additional VCS info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from .git/config file.

Thanks to Oscar Alberto Tovar for discovering the issue.

Impact

When a build is performed under specific conditions where credentials were passed to BuildKit they may be visible to everyone who has access to provenance attestation.

Provenance attestations and VCS info hints were added in version v0.11.0. Previous versions are not vulnerable.

In v0.10, when building directly from Git URL, the same URL could be visible in BuildInfo structure that is a predecessor of Provenance attestations. Previous versions are not vulnerable.

Note: Docker Build-push Github action builds from Git URLs by default but is not affected by this issue even when working with private repositories because the credentials are passed with build secrets and not with URLs.

Patches

Bug is fixed in v0.11.4 .

Workarounds

It is recommended to pass credentials with build secrets when building directly from Git URL as a more secure alternative than modifying the URL.

In Docker Buildx, VCS info hint can be disabled by setting BUILDX_GIT_INFO=0. buildctl does not set VCS hints based on .git directory, and values would need to be passed manually with --opt.

References

Inline credentials in URLs deprecated in RFC3986 https://www.rfc-editor.org/rfc/rfc3986#section-3.2.1

Fixed in


          0.11.4

References

Updated Nov 08, 2023 · Source: OSV.dev

Feb 13, 2023

v0.11.1 minor

7 CVEs

CVE-2026-33747 GO-2026-4858 GHSA-4c29-8rgm-jvjj Mar 27, 2026

BuildKit's Malicious frontend can cause file escape outside of storage root in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2026-33748 GO-2026-4859 GHSA-4vrq-3vrq-g6gg Mar 27, 2026

BuildKit Git URL subdir component can cause access to restricted files in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2024-23651 GO-2024-2493 GHSA-m3r6-h7wv-7xxv Feb 13, 2024

Host system file access in github.com/moby/buildkit

Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container.

Fixed in


          0.12.5

References

https://github.com/moby/buildkit/pull/4604

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23650 GO-2024-2492 GHSA-9p26-698r-w4hx Feb 12, 2024

Panic in github.com/moby/buildkit

A malicious BuildKit client or frontend could craft a request that could lead to a BuildKit daemon crashing with a panic.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23652 GO-2024-2494 GHSA-4v98-7qmw-rqr8 Feb 12, 2024

Host system modification in github.com/moby/buildkit

A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23653 GO-2024-2497 GHSA-wr6v-9f75-vh2g Feb 07, 2024

Privilege escalation in github.com/moby/buildkit

BuildKit provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special security.insecure entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2023-26054 GHSA-gc89-7gcr-jxqc Mar 07, 2023

Buildkit credentials inlined to Git URLs could end up in provenance attestation

6.5 / 10

Medium

Network Low None Required Unchanged High None None

When the user sends a build request that contains a Git URL that contains credentials and the build creates a provenance attestation describing that build, these credentials could be visible from the provenance attestation.

Git URL can be passed in two ways:

Invoking build directly from a URL with credentials.

buildctl build --frontend dockerfile.v0 --context https://<credentials>@url/repo.git

Equivalent in docker buildx would be

docker buildx build https://<credentials>@url/repo.git

If the client sends additional VCS info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from .git/config file.

Thanks to Oscar Alberto Tovar for discovering the issue.

Impact

When a build is performed under specific conditions where credentials were passed to BuildKit they may be visible to everyone who has access to provenance attestation.

Provenance attestations and VCS info hints were added in version v0.11.0. Previous versions are not vulnerable.

In v0.10, when building directly from Git URL, the same URL could be visible in BuildInfo structure that is a predecessor of Provenance attestations. Previous versions are not vulnerable.

Note: Docker Build-push Github action builds from Git URLs by default but is not affected by this issue even when working with private repositories because the credentials are passed with build secrets and not with URLs.

Patches

Bug is fixed in v0.11.4 .

Workarounds

It is recommended to pass credentials with build secrets when building directly from Git URL as a more secure alternative than modifying the URL.

In Docker Buildx, VCS info hint can be disabled by setting BUILDX_GIT_INFO=0. buildctl does not set VCS hints based on .git directory, and values would need to be passed manually with --opt.

References

Inline credentials in URLs deprecated in RFC3986 https://www.rfc-editor.org/rfc/rfc3986#section-3.2.1

Fixed in


          0.11.4

References

Updated Nov 08, 2023 · Source: OSV.dev

Jan 17, 2023

v0.11.0-rc4 pre

7 CVEs

CVE-2026-33747 GO-2026-4858 GHSA-4c29-8rgm-jvjj Mar 27, 2026

BuildKit's Malicious frontend can cause file escape outside of storage root in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2026-33748 GO-2026-4859 GHSA-4vrq-3vrq-g6gg Mar 27, 2026

BuildKit Git URL subdir component can cause access to restricted files in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2024-23651 GO-2024-2493 GHSA-m3r6-h7wv-7xxv Feb 13, 2024

Host system file access in github.com/moby/buildkit

Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container.

Fixed in


          0.12.5

References

https://github.com/moby/buildkit/pull/4604

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23650 GO-2024-2492 GHSA-9p26-698r-w4hx Feb 12, 2024

Panic in github.com/moby/buildkit

A malicious BuildKit client or frontend could craft a request that could lead to a BuildKit daemon crashing with a panic.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23652 GO-2024-2494 GHSA-4v98-7qmw-rqr8 Feb 12, 2024

Host system modification in github.com/moby/buildkit

A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23653 GO-2024-2497 GHSA-wr6v-9f75-vh2g Feb 07, 2024

Privilege escalation in github.com/moby/buildkit

BuildKit provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special security.insecure entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2023-26054 GHSA-gc89-7gcr-jxqc Mar 07, 2023

Buildkit credentials inlined to Git URLs could end up in provenance attestation

6.5 / 10

Medium

Network Low None Required Unchanged High None None

When the user sends a build request that contains a Git URL that contains credentials and the build creates a provenance attestation describing that build, these credentials could be visible from the provenance attestation.

Git URL can be passed in two ways:

Invoking build directly from a URL with credentials.

buildctl build --frontend dockerfile.v0 --context https://<credentials>@url/repo.git

Equivalent in docker buildx would be

docker buildx build https://<credentials>@url/repo.git

If the client sends additional VCS info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from .git/config file.

Thanks to Oscar Alberto Tovar for discovering the issue.

Impact

When a build is performed under specific conditions where credentials were passed to BuildKit they may be visible to everyone who has access to provenance attestation.

Provenance attestations and VCS info hints were added in version v0.11.0. Previous versions are not vulnerable.

In v0.10, when building directly from Git URL, the same URL could be visible in BuildInfo structure that is a predecessor of Provenance attestations. Previous versions are not vulnerable.

Note: Docker Build-push Github action builds from Git URLs by default but is not affected by this issue even when working with private repositories because the credentials are passed with build secrets and not with URLs.

Patches

Bug is fixed in v0.11.4 .

Workarounds

It is recommended to pass credentials with build secrets when building directly from Git URL as a more secure alternative than modifying the URL.

In Docker Buildx, VCS info hint can be disabled by setting BUILDX_GIT_INFO=0. buildctl does not set VCS hints based on .git directory, and values would need to be passed manually with --opt.

References

Inline credentials in URLs deprecated in RFC3986 https://www.rfc-editor.org/rfc/rfc3986#section-3.2.1

Fixed in


          0.11.4

References

Updated Nov 08, 2023 · Source: OSV.dev

Jan 06, 2023

v0.11.0-rc2 pre

7 CVEs

CVE-2026-33747 GO-2026-4858 GHSA-4c29-8rgm-jvjj Mar 27, 2026

BuildKit's Malicious frontend can cause file escape outside of storage root in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2026-33748 GO-2026-4859 GHSA-4vrq-3vrq-g6gg Mar 27, 2026

BuildKit Git URL subdir component can cause access to restricted files in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2024-23651 GO-2024-2493 GHSA-m3r6-h7wv-7xxv Feb 13, 2024

Host system file access in github.com/moby/buildkit

Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container.

Fixed in


          0.12.5

References

https://github.com/moby/buildkit/pull/4604

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23650 GO-2024-2492 GHSA-9p26-698r-w4hx Feb 12, 2024

Panic in github.com/moby/buildkit

A malicious BuildKit client or frontend could craft a request that could lead to a BuildKit daemon crashing with a panic.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23652 GO-2024-2494 GHSA-4v98-7qmw-rqr8 Feb 12, 2024

Host system modification in github.com/moby/buildkit

A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23653 GO-2024-2497 GHSA-wr6v-9f75-vh2g Feb 07, 2024

Privilege escalation in github.com/moby/buildkit

BuildKit provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special security.insecure entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2023-26054 GHSA-gc89-7gcr-jxqc Mar 07, 2023

Buildkit credentials inlined to Git URLs could end up in provenance attestation

6.5 / 10

Medium

Network Low None Required Unchanged High None None

When the user sends a build request that contains a Git URL that contains credentials and the build creates a provenance attestation describing that build, these credentials could be visible from the provenance attestation.

Git URL can be passed in two ways:

Invoking build directly from a URL with credentials.

buildctl build --frontend dockerfile.v0 --context https://<credentials>@url/repo.git

Equivalent in docker buildx would be

docker buildx build https://<credentials>@url/repo.git

If the client sends additional VCS info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from .git/config file.

Thanks to Oscar Alberto Tovar for discovering the issue.

Impact

When a build is performed under specific conditions where credentials were passed to BuildKit they may be visible to everyone who has access to provenance attestation.

Provenance attestations and VCS info hints were added in version v0.11.0. Previous versions are not vulnerable.

In v0.10, when building directly from Git URL, the same URL could be visible in BuildInfo structure that is a predecessor of Provenance attestations. Previous versions are not vulnerable.

Note: Docker Build-push Github action builds from Git URLs by default but is not affected by this issue even when working with private repositories because the credentials are passed with build secrets and not with URLs.

Patches

Bug is fixed in v0.11.4 .

Workarounds

It is recommended to pass credentials with build secrets when building directly from Git URL as a more secure alternative than modifying the URL.

In Docker Buildx, VCS info hint can be disabled by setting BUILDX_GIT_INFO=0. buildctl does not set VCS hints based on .git directory, and values would need to be passed manually with --opt.

References

Inline credentials in URLs deprecated in RFC3986 https://www.rfc-editor.org/rfc/rfc3986#section-3.2.1

Fixed in


          0.11.4

References

Updated Nov 08, 2023 · Source: OSV.dev

Dec 13, 2022

v0.10.6 patch

7 CVEs

CVE-2026-33747 GO-2026-4858 GHSA-4c29-8rgm-jvjj Mar 27, 2026

BuildKit's Malicious frontend can cause file escape outside of storage root in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2026-33748 GO-2026-4859 GHSA-4vrq-3vrq-g6gg Mar 27, 2026

BuildKit Git URL subdir component can cause access to restricted files in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2024-23651 GO-2024-2493 GHSA-m3r6-h7wv-7xxv Feb 13, 2024

Host system file access in github.com/moby/buildkit

Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container.

Fixed in


          0.12.5

References

https://github.com/moby/buildkit/pull/4604

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23650 GO-2024-2492 GHSA-9p26-698r-w4hx Feb 12, 2024

Panic in github.com/moby/buildkit

A malicious BuildKit client or frontend could craft a request that could lead to a BuildKit daemon crashing with a panic.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23652 GO-2024-2494 GHSA-4v98-7qmw-rqr8 Feb 12, 2024

Host system modification in github.com/moby/buildkit

A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23653 GO-2024-2497 GHSA-wr6v-9f75-vh2g Feb 07, 2024

Privilege escalation in github.com/moby/buildkit

BuildKit provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special security.insecure entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2023-26054 GHSA-gc89-7gcr-jxqc Mar 07, 2023

Buildkit credentials inlined to Git URLs could end up in provenance attestation

6.5 / 10

Medium

Network Low None Required Unchanged High None None

When the user sends a build request that contains a Git URL that contains credentials and the build creates a provenance attestation describing that build, these credentials could be visible from the provenance attestation.

Git URL can be passed in two ways:

Invoking build directly from a URL with credentials.

buildctl build --frontend dockerfile.v0 --context https://<credentials>@url/repo.git

Equivalent in docker buildx would be

docker buildx build https://<credentials>@url/repo.git

If the client sends additional VCS info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from .git/config file.

Thanks to Oscar Alberto Tovar for discovering the issue.

Impact

When a build is performed under specific conditions where credentials were passed to BuildKit they may be visible to everyone who has access to provenance attestation.

Provenance attestations and VCS info hints were added in version v0.11.0. Previous versions are not vulnerable.

In v0.10, when building directly from Git URL, the same URL could be visible in BuildInfo structure that is a predecessor of Provenance attestations. Previous versions are not vulnerable.

Note: Docker Build-push Github action builds from Git URLs by default but is not affected by this issue even when working with private repositories because the credentials are passed with build secrets and not with URLs.

Patches

Bug is fixed in v0.11.4 .

Workarounds

It is recommended to pass credentials with build secrets when building directly from Git URL as a more secure alternative than modifying the URL.

In Docker Buildx, VCS info hint can be disabled by setting BUILDX_GIT_INFO=0. buildctl does not set VCS hints based on .git directory, and values would need to be passed manually with --opt.

References

Inline credentials in URLs deprecated in RFC3986 https://www.rfc-editor.org/rfc/rfc3986#section-3.2.1

Fixed in


          0.11.4

References

Updated Nov 08, 2023 · Source: OSV.dev

Nov 10, 2022

v0.10.4 minor

7 CVEs

CVE-2026-33747 GO-2026-4858 GHSA-4c29-8rgm-jvjj Mar 27, 2026

BuildKit's Malicious frontend can cause file escape outside of storage root in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2026-33748 GO-2026-4859 GHSA-4vrq-3vrq-g6gg Mar 27, 2026

BuildKit Git URL subdir component can cause access to restricted files in github.com/moby/buildkit

Fixed in


          0.28.1

References

Updated Mar 28, 2026 · Source: OSV.dev

CVE-2024-23651 GO-2024-2493 GHSA-m3r6-h7wv-7xxv Feb 13, 2024

Host system file access in github.com/moby/buildkit

Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container.

Fixed in


          0.12.5

References

https://github.com/moby/buildkit/pull/4604

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23650 GO-2024-2492 GHSA-9p26-698r-w4hx Feb 12, 2024

Panic in github.com/moby/buildkit

A malicious BuildKit client or frontend could craft a request that could lead to a BuildKit daemon crashing with a panic.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23652 GO-2024-2494 GHSA-4v98-7qmw-rqr8 Feb 12, 2024

Host system modification in github.com/moby/buildkit

A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2024-23653 GO-2024-2497 GHSA-wr6v-9f75-vh2g Feb 07, 2024

Privilege escalation in github.com/moby/buildkit

BuildKit provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special security.insecure entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request.

Fixed in


          0.12.5

References

Updated Feb 04, 2026 · Source: OSV.dev

CVE-2023-26054 GHSA-gc89-7gcr-jxqc Mar 07, 2023

Buildkit credentials inlined to Git URLs could end up in provenance attestation

6.5 / 10

Medium

Network Low None Required Unchanged High None None

When the user sends a build request that contains a Git URL that contains credentials and the build creates a provenance attestation describing that build, these credentials could be visible from the provenance attestation.

Git URL can be passed in two ways:

Invoking build directly from a URL with credentials.

buildctl build --frontend dockerfile.v0 --context https://<credentials>@url/repo.git

Equivalent in docker buildx would be

docker buildx build https://<credentials>@url/repo.git

If the client sends additional VCS info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from .git/config file.

Thanks to Oscar Alberto Tovar for discovering the issue.

Impact

When a build is performed under specific conditions where credentials were passed to BuildKit they may be visible to everyone who has access to provenance attestation.

Provenance attestations and VCS info hints were added in version v0.11.0. Previous versions are not vulnerable.

In v0.10, when building directly from Git URL, the same URL could be visible in BuildInfo structure that is a predecessor of Provenance attestations. Previous versions are not vulnerable.

Note: Docker Build-push Github action builds from Git URLs by default but is not affected by this issue even when working with private repositories because the credentials are passed with build secrets and not with URLs.

Patches

Bug is fixed in v0.11.4 .

Workarounds

It is recommended to pass credentials with build secrets when building directly from Git URL as a more secure alternative than modifying the URL.

In Docker Buildx, VCS info hint can be disabled by setting BUILDX_GIT_INFO=0. buildctl does not set VCS hints based on .git directory, and values would need to be passed manually with --opt.

References

Inline credentials in URLs deprecated in RFC3986 https://www.rfc-editor.org/rfc/rfc3986#section-3.2.1

Fixed in


          0.11.4

References

Updated Nov 08, 2023 · Source: OSV.dev

Aug 22, 2022

v0.10.0-rc1 pre

6 CVEs

Feb 14, 2022

v0.9.1 minor

6 CVEs

Oct 04, 2021

v0.9.0-rc2 pre

6 CVEs

Jul 16, 2021

v0.8.2 minor

6 CVEs

Feb 25, 2021

v0.8.0-rc3 pre

6 CVEs

Nov 26, 2020

v0.7.1 minor

6 CVEs

Apr 16, 2020

v0.6.4 patch

6 CVEs

Feb 21, 2020

v0.6.3 minor

6 CVEs

Nov 13, 2019

v0.3.2 initial

6 CVEs

Oct 31, 2018

Activity

Reach

Details

Impact

Patches

Workarounds

References

Impact

Patches

Workarounds

References

Impact

Patches

Workarounds

References

Impact

Patches

Workarounds

References

Impact

Patches

Workarounds

References

Impact

Patches

Workarounds

References

Impact

Patches

Workarounds

References